QIPP Digital Technology and ITK Care Co-Ordination: Interoperability WebEx4. 14 th November 2012. WebEx. Overview of the end-to-end basic “store, notify and retrieve” interaction pattern Get Document – considered and chosen options Get Document serialisation options
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Note: This is only an example!
These aspects have been discussed in workshops but out of scope of specification for now
From previous example – e.g. GP system
Been discussed but out of scope for now
e.g. OOH system
Option 1: Get document by specific document/documentset id
Option 2: Get document by other unique identifier (e.g. UBRN)
Option 3: Get document by document type
Option 4: Optimised “Get Document List”
ITK message in standard wrappers (e.g. SOAP for WS, DistributionEnvelope for all transports)
HL7v3 payload message
BusinessAck – for errors
HL7 response wrappers + CDA payload
Patient Identity Source
Patient Identity feed
Get Document List
Chosen because it is simplest and future compatible with the full registry / repository pattern
Requires the least amount of up-front analysis whilst still satisfying the core QIPP EPaCCS use-case
Creates a dependency on the Notification capability
Probably requires around 50% of the analysis for the Get Document List/meta-data needs to be complete to ensure the transaction is future proof.