ITI TI Supp Updates to FHIR STU3: Difference between revisions
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| Line 11: | Line 11: | ||
== FHIR DSTU2 to STU3 mapping == | == FHIR DSTU2 to STU3 mapping == | ||
Note that DSTU and STU are "Trial Use", which means there is no guarantee that a change from one version to another will be compatible. STU3 has extra effort to provide a mapping. This information can be found in the FHIR specification | Note that DSTU and STU are "Trial Use", which means there is no guarantee that a change from one version to another will be compatible. STU3 has extra effort to provide a mapping. This information can be found in the FHIR specification. There is a drill down for each Resource mapping, and details on how to automatically transform. | ||
* Differences between DSTU2 and STU3 http://build.fhir.org/diff.html | * Differences between DSTU2 and STU3 http://build.fhir.org/diff.html | ||
| Line 17: | Line 17: | ||
Also tools like HAPI can support both versions at the same time. | Also tools like HAPI can support both versions at the same time. | ||
Two perspectives on this data is important: | |||
# To show our reader the impact of DSTU2 to STU3; to help them understand the impact to any code they might have. | |||
# To use by editors, to guide editing of Profile text. | |||
Our profile text should NOT concern with the translation. They should only document STU3 profiling. Do not include mapping, except possibly in throwaway introduction text such as a "Closed Issue" to help our reader find this information. | |||
== Notes & Analysis == | == Notes & Analysis == | ||
Revision as of 12:32, 13 March 2017
This wiki page is used by the ITI TC to collaborate and plan for updating ITI Supplements from FHIR DSTU2 to STU3. This page is not owned by anyone. To contribute...edit it.
Short summary of updates needed
- Add RESTful Query to ATNA -
- Appendix Z -
- mACM -
- MHD -
- PDQm-
- PIXm - we have the opportunity to include a review of supplement defyning a new pattern (following the approach used in FHIR to cross-reference API).
FHIR DSTU2 to STU3 mapping
Note that DSTU and STU are "Trial Use", which means there is no guarantee that a change from one version to another will be compatible. STU3 has extra effort to provide a mapping. This information can be found in the FHIR specification. There is a drill down for each Resource mapping, and details on how to automatically transform.
- Differences between DSTU2 and STU3 http://build.fhir.org/diff.html
- Transforms between DSTU2 and STU3 http://build.fhir.org/r2maps.html
Also tools like HAPI can support both versions at the same time.
Two perspectives on this data is important:
- To show our reader the impact of DSTU2 to STU3; to help them understand the impact to any code they might have.
- To use by editors, to guide editing of Profile text.
Our profile text should NOT concern with the translation. They should only document STU3 profiling. Do not include mapping, except possibly in throwaway introduction text such as a "Closed Issue" to help our reader find this information.
Notes & Analysis
- Notes from the Feb ITI F2F:
- MHD, PDQ, RESTful ATNA will be easy to update. The amount of work needed to move from DSTU2 to STU3 is less then what we've done last years.
- mACM: could have significant changes, (this is the RISKY point, there could be a push to change the process).
- The cmte agreed on Sending a request out to Vendors of CAT and other interested parties (specific implementers google groups) describing our intent to update the supplements. The contact list of people interested will be created by Lynn, John will prepare the email.
Open CPs
| CP-ITI | Title | Doc | Assignee | Notes |
|---|---|---|---|---|
| 1005 | RESTful ATNA update to FHIR STU3 | RESTful ATNA | Mauro | |
| 1006 | mACM updates to FHIR STU3 | mACM | Luke | |
| 940 | ITI-65 should specify how to link to the Binary resource from the DocumentReference | MHD | Walco | |
| 941 | Encoding of UUIDs and OIDs in Identifiers | MHD | Walco | |
| 942 | Encoding of XDSDocumentEntry.referenceIdList in FHIR DocumentReference resource | MHD | Walco | |
| 943 | Encoding of XDSDocumentEntry.uniqueId in FHIR Identifier | MHD | John | |
| 944 | Clarification of hash and size attributes in FHIR | MHD | John | |
| 945 | ITI-65 should define how to reference patients in a provide transaction | MHD | John | |
| 946 | ITI-65 Provide Bundle response status codes should be clarified | MHD | John | |
| 1002 | MHD update to FHIR STU3 | MHD | John | |
| 1007 | Appendix Z updates to FHIR STU3 | Appx Z | John | |
| 826 | PDQm - Clarify requirements for Pediatric Demographics | PDQm | Justin | |
| 1003 | PDQm update to FHIR STU3 | PDQm | John | |
| 1011 | PDQm Case 3 – HTTP Return Code clarification | PDQm | John | |
| 1004 | PIXm update to FHIR STU3 | PIXm | John |
Other considerations
Significant Dates
- Link to FHIR publication schedule: http://wiki.hl7.org/index.php?title=FHIR_Ballot_Prep
- Mar 23 - CP call for mobile bundle
- Mar 30 - CP call for mobile bundle
- Apr 24-28 - ITI TC F2F in Oak Brook
- The following is the current timeline for republishing existing TF Vols & TI Supplements updated by CPs in 2017
- May 15 - deadline for CPs to reach Final Text status in order to be integrated
- May 15-June 23 - editors integrate CPs and internal review of integrations
- June 26 - editors deliver updated docs to Mary
- June 16 - July 15 - Mary works on repub & iterates w/ co-chairs, editors & lynn to review
- July 30 - updated TF volumes & TI Supps are published on ihe.net
- July 17-21 - ITI TC F2F in Oak Brook