Difference between revisions of "Multi-Patient Queries"
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
Line 55: | Line 55: | ||
[[Category:Profiles]] | [[Category:Profiles]] | ||
[[Category:ITI Profile]] | [[Category:ITI Profile]] | ||
+ | [[Category:DocShare]] | ||
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]]. | Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]]. |
Revision as of 14:59, 20 July 2017
Summary
The Multi-Patient Queries profile defines a mechanism to enable aggregated queries to a Document Registry based on certain criteria needed by areas related to data analysis, such as quality accreditation of health care practitioners or health care facilities, clinical research trial data collection or population health monitoring.
Benefits
Allows clinical research, quality accreditation institutions and public health organizations to make sound decisions in their field of activity.
Details
Currently, the Stored Query transaction [ITI-18] defines a single catalog of queries, which require that either a single patient ID, a folder ID, or a submission set ID are present in each query. While the existing query catalog serves various healthcare integration workflows, there are other cases where aggregated queries, i.e. queries not constrained to a single patient, folder, or catalog, are necessary. The domain that is currently needing the aggregated queries is the QRPH (the Quality, Research and Public Health), where data needs to be combined so that a pattern can ensue. Examples in the three areas would be repurposing, secondary use, and monitoring population health.
Quality accreditation organizations need to be able to aggregate data so that they can perform measurements of how institutions perform (author or healthcareFacilityTypeCode).
Clinical Research needs to be able to combine the results of different patients in a clinical trial (typeCode).
Public Health needs to have the means to make aggregated queries on certain fields such as eventCodeList in order to identify potential outbreaks and take appropriate decisions.
Systems Affected
Systems involved in this profile are:
- Quality accreditation organizations, Clinical Research and Public Health systems
Actors & Transactions:
Specification
Profile Status: Final Text
Documents:
- Vol. 1 - Section 25
- Vol. 2a - Sections 3.18
- Vol. 2b - Sections 3.51
- Vol. 3 - Section 4.1, 4.2, 4.3
Underlying Standards:
- ebRIM OASIS/ebXML Registry Information Model v3.0
- ebRS OASIS/ebXML Registry Services Specifications v3.0
See Also
This page is based on the Profile Template
Current: IT Infrastructure Technical Framework.