Difference between revisions of "Mobile access to Health Documents - Supplement revision 2"

Revision as of 10:05, 28 February 2014

This work item strives to revise the MHD profile supplement to align with the HL7 FHIR standard that has entered DSTU phase.

Mapping each XDS object/attribute to FHIR, and back
- Bill Majurski
Scope of MHD vs FHIR
- John Moehrke
- Reevaluation of target audience. Are the limitations we put into MHD still the right limitations, or should we relax them if we can?
- Rationalize IHE specifically only providing JSON, yet FHIR has both.
- MHD supports only one document in one submissionSet
- MHD does one transaction to publish
- do we add Options to MHD to support more complex interactions?
FHIR Provenance Resource Mapping
- Rob Horn
Transport Pattern Mapping
- Walco Van Loon
- FHIR has many transaction patterns -- REST, Mailbox, etc.
- Publication in MHD is one transaction
Analysis of FHIR and IHE Lifecycle
- Erik Pupo
- How to handle PatientInfo, as FHIR would tend to simply update a master PatientInfo where in XDS this information is stored as is.
- Document relationships
Tracking and Monitoring of business level changes (politics) and outreach
- Erik Pupo

Minutes are found on the Discussion

Sub-Workgroup meeting

The root http://hl7.org/fhir
This is the library of all currently defined ‘resources’ http://hl7.org/implement/standards/fhir/resourcelist.html
- Specific to PDQm but will also be used in MHD
  - Patient
  - RelatedPerson
- Specific to MHD
  - DocumentReference
  - DocumentManifest
  - Provenance
  - List
Here is the “Profile” that Grahame did inside of FHIR of how FHIR can map to XDS
Note also specific to a future effort on ATNA
- SecurityEvent

@@ Line 1: / Line 1: @@
 This work item strives to revise the [[MHD]] profile supplement to align with the HL7 FHIR standard that has entered DSTU phase.
-== Areas where details need to be worked out ==
+== Current Status and Directions ==
 * Mapping each XDS object/attribute to FHIR, and back
 ** Bill Majurski