IHE Profiles and FHIR (2)
summary
Explains how MHD acts as a REST/JSON API into XDS/XCA: clients push a Bundle with a DocumentManifest, one or more DocumentReference and Binary pairs (CDA XML, PDF, or FHIR-as-transform), and query document metadata over HTTP instead of ebXML/SOAP; responders can negotiate content type and optionally convert CCDA to FHIR. For data extraction the QED/MHD pattern runs a decomposition engine that emits FHIR Observations/Medications and links each extracted item back to originals via one or more Provenance resources so consumers can trace and trust the source.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:54Overview
- 2:15Health Information Exchange
- 3:20Cross Community Access
- 3:56Health Information Exchanges
- 4:17CDA Principles
- 7:45Contacting Context
- 9:37Metadata
- 10:10MHD
- 14:01XDS
- 14:47Patient Lookup
- 15:06MHD Publishing
- 18:31MHD Receiving
- 20:40Publication
- 25:42Conformance Resources
- 26:31Why JSON
- 27:38QED
- 29:23Document Data Element Extraction
- 30:56Document Provenance
- 32:54Provenance Resources
- 35:19Conclusion
- 35:43Questions
related talks
45mXDS on FHIR
41mFHIR Documents
46mIntroduction to FHIR Messages and FHIR Documents
33mSponsored by DMI: This could have been a Questionnaire
22mDanish FHIR – how legacy gets FHIR’ed
18mRelevant technologies for CMS-0057-P and CMS-0053-P
46mHEDIS on FHIR: NCQA’s digital transformation
43mFHIR® Roadmap for TEFCA Exchange