QDA Work Item ProposalFebruary 10-14th, Vienna IHE F2F meeting
Vincent van Pelt, Albert-Jan Spruyt (Nictiz)Mark Sinke, Walco van Loon (ForCare)
QDA – Business case
· Summaries are made by aggregating information from often different sources
· Need for a profile that can take care of complex multi-query creation
QDA – Use Cases
· Medication Summary
· Prescriptions
· Dispensations
· Allergies interactions contra-indications
· Relevant lab values
· Relevant diagnoses
· Patient Summary
· From multiple sources; ‘Blue button’
· Emergency Care Summary
· Combined information from emergency call center, ambulance, Emergency department, ICU
· Integrated Care Overview
· Combined information from PCP, dietician, physiotherapist, laboratory
QDA – Query Dispatch and Aggregate
· Generic tool for the creation of multi-source summaries and aggregated reports
· One report request, multiple subqueries, one report result
· Can collect information from database queries, existing documents, and other methods
Purposes
· Can be called by ODD (On Demand Document) to create documents from multiple sources (including non-IHE) to create on-the fly actual information
· Can be used by any Actor that needs a summary (view) from multiple existing documents
XDS
Provide and Register Document Set (ITI-41)
Retrieve Document Set (ITI-43)
RegisterDocument Set (ITI-42)
Registry StoredQuery (ITI-18)
Document Registry
DocumentSource
DocumentRepository
DocumentConsumer
Register On-DemandDocument Entry (ITI-61)
XDS + ODD
Provide and Register Document Set (ITI-41)
Retrieve Document Set (ITI-43)
RegisterDocument Set (ITI-42)
Registry StoredQuery (ITI-18)
Document Registry
DocumentSource
DocumentRepository
DocumentConsumer
On-DemandDocument Source
Register On-DemandDocument Entry (ITI-61)
XDS + ODD (+ persistent storage)
Provide and Register Document Set (ITI-41)
Retrieve Document Set (ITI-43)
RegisterDocument Set (ITI-42)
Registry StoredQuery (ITI-18)
Document Registry
DocumentSource
DocumentRepository
DocumentConsumer
On-DemandDocument Source
Provide and Register Document Set (ITI-41)
Register On-DemandDocument Entry (ITI-61)
XDS + ODD + QDA
Provide and Register Document Set (ITI-41)
Retrieve Document Set (ITI-43)
RegisterDocument Set (ITI-42)
Registry StoredQuery (ITI-18)
Document Registry
DocumentSource
DocumentRepository
DocumentConsumer
On-DemandDocument Source
QDA Content Source
Create Multi-Source Summary
Provide and Register Document Set (ITI-41)
XDS
• XDS Retrieve Document Set• XCA Query and Retrieve• HL7 Care Record Query• QED• RESTful: FHIR, JSON, MHD• Web Service• ANSI SQL• . ..?
EHR
Pharmacy
Laboratory
Radiology
Pathology
Intra-andCross-community
Register On-DemandDocument Entry (ITI-61)
XDS + ODD + QDA + RECON
Provide and Register Document Set (ITI-41)
Retrieve Document Set (ITI-43)
RegisterDocument Set (ITI-42)
Registry StoredQuery (ITI-18)
Document Registry
DocumentSource
DocumentRepository
DocumentConsumer
On-DemandDocument Source
QDA Content Source
Create Multi-Source Summary
Provide and Register Document Set (ITI-41)
RECON
Share Content
XDS
• XDS Retrieve Document Set• XCA Query and Retrieve• HL7 Care Record Query• QED• RESTful: FHIR, JSON, MHD• Web Service• XCF• ANSI SQL• ...?
EHR
Pharmacy
Laboratory
Radiology
Pathology
Intra-andCross-community
QDA parameters
• Report ID
• Patient ID
• Summaryformat• Collate• Reconcile
• From-datetime
• To-datetime
• ToFormat• HL7 CDA• HL7 V2 message• HL7 V3 Message• XML document
Request • Query ID
• Requestor ID (org. and person?)
• Patient ID
• Query Method• XDS Retrieve Document Set• XCA Query and Retrieve• HL7 Care Record Query• QED• RESTful: FHIR, JSON, MHD• Web Service• ANSI SQL• . ..?
• Query Target (institution)
• Required document template (OID)
• Query string (OID)
•
Dispatch • ‘Stitch’, collate to 1 doc
• Use RECON to reconciliate
• Message wrapper?
Aggregate
Remarks· Some parts of the functionality can be covered by existing profiles. However, some functionality is
missing:
· Transforming documents / messages / webservices from different sources into one document
· Receiving one report request, and then sendif a number of preformatted subqueries
· Configurable subqueries
· Add RECON / MCV / DEN / DSG etcetera to format and create the result-document
· Content Creator
Remarks
Profile or Whitepaper?o A lot of IHE profiles start as whitepapero If there are “holes” in existing profiles, it would definitely warrant a profileo IHE/ITI: pure configuration management profiles often don’t make it through the first selectiono Find synergy with DAF (recipe for existing problems) / RECON (aggregation) ? XCF is not the wholeanswer:o Is an optimization of XCA Query and Retrieveo It does not aggregate results into one documento Is not plug and play with ODD: there is no way to snapshot the resultsBut it can be used as one of the ‘fetch’ options · Presentationo You might want to make the diagram/text more clear that you want to further profile/describe/specify the currently opaque ODD Document Source. This is probably not clear to people right now. QDA Content Source seems to be a separate actor interacting with a ODD Document Source. Maybe create a new diagram with just the new actors/transactions.
Behavioral pattern
Remarks
o How can a profile like qed / XCF know which subqueries it needs to perform to aggregate the summary?
Behavioral patternActivity diagramSynchronous and asynchronous queries