Updates of Profiles to FHIR DSTU2

From IHE Wiki
Revision as of 13:35, 4 December 2015 by ELavy (talk | contribs) (→‎Punch List of changes: clarification on "style of auditing" line-item)
Jump to navigation Jump to search

This page holds the overall plan (current a work-in-progress) for updating the IHE Profiles to FHIR DSTU2. The purpose is to ensure consistency of updates across affected IHE profiles.

Meeting

Bi-Weekly: Starting November 23, 2015 https://himss.webex.com/himss/j.php?MTID=m9db38c21ca7f849cf3ca6f9c5c88dc4c

Timeline

Goal is to have the updates ready for EU connectathon. This means:

  • done with the CP ballot by March 1
  • into ballot by February 1

List of Profiles to be updated

In ITI, Initial work is being done using CPs. These are found in ITI's Assigned directory for CPs:

  • MHD - CP-ITI-886 - assigned to John Moehrke -- again tracking on MHD Status
  • PDQm - CP-ITI-885 - assigned to Justin Fyfe
  • PIXm - CP-ITI-884 - assigned to Daniel Berezeanu
  • mACM - CP-ITI-883 - assigned to Carl Leitner
  • RESTful ATNA Query - CP-ITI-887 - assigned to Rob Horn

In PCC, ????:

  • CMAP
  • GAO
  • RECON

Task

Ask that the sub-workgroup participants review the current IHE profiles in the context of finding areas that need to be aligned with DSTU2"

  1. (see punch list) -- and update punch list
  2. Where the FHIR specification changed and we need to align
  3. Where there are other improvement opportunities.
  4. Opportunities to move common FHIR stuff to Appendix Z (currently found in PDQm)
  5. Evaluate if we are using "frozen" FHIR resources, or unstable ones (Some FHIR resources have been declared frozen, meaning they will not be part of DSTU 2.1 ballot in the spring, while others are less stable and will be subject to DSTU 2.1 ballot).


Assignments:

  • Paul -- PIXm and PDQm
  • Jim -- mACM
  • Mauro -- RESTful ATNA

Working Directory

Working Directory: ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Technical%20Cmte/Workitems/DSTU2updates/

  • sub-workgroup participants use WORD change-tracking to add comments and corrections
  • Save your updates to the FTP using a new date or your initials in the filename

Punch List of changes

There are some things that need to be done consistently for all profiles of FHIR. There are other things that need to be unique to each profile. Profile specific changes are managed independently of this punch list.

  • Align on DSTU2 final published http://hl7.org/fhir/DSTU2/index.html
  • Make sure the URLs to the FHIR specification are fully specified and accurate.
  • FHIR section numbers
    • Some section numbers have changed between DSTU2 and earlier versions. Each TI Supplement needs to be reviewed to ensure FHIR section numbers are still accurate.
    • Need a consistent way to use FHIR section numbers that are distinct from IHE section numbers. For example when we refer into the FHIR specification (e.g. when referencing the Signature data type we could use "1.19.0.16 Signature", or could use the anchor URL http://hl7.org/fhir/DSTU2/datatypes.html#signature). If using the section numbers (e.g. 1.19.0.16) it needs to be clear that is a FHIR spec number, not an IHE profile number. -- Might we define a prefix "fhir:1.19.0.16"
  • Where we have duplicated FHIR specification using methods other than by-reference or perfect-copy. For example where we have copied FHIR specification and changed the format.
  • Opportunity to improve readability or implementation
    • Where we might need to explain how to translate between companion profiles
      • For example where a PDQ query exists, show how to do the same query in PDQm
  • How do we manage those supplements that are profiling 'frozen' Resources from those that are subject to DSTU 2.1 ballot (e.g., ATNA - AuditEvent)
    • Clearly identification as Open-Issue in that supplement.
  • Create a HL7 balloted and published FHIR Profile
  • Focus on Appendix Z -- the shared appendix on FHIR Implementation Materials
    • Should we extract out Appendix Z from PDQm? Thus making it more obvious as a shared appendix?
    • What should be added to Appendix Z?
  • Use the same definition of "Mobile", look to RESTful ATNA for current-best-explaination.
  • Similar Audit Logging
    • To address the fact that mobile clients are sometimes underpowered and thus don't have the ability to do all the audit logging we normally expect of a client use the text "should send audit messages if possible" for the client side.
    • Consider changing the style of auditing for PIXm and PDQm to be like what Elliott L tried doing for MHD in CP-ITI-891. That is, rather than duplicate the whole audit message table, reference the normal profile and express the delta.


...more TBD (feel free to edit this list...this page is not owned by one person)

Profile-specific

In addition to the updates being doing consistently across profiles, some supplements will need profile-specific changes.

  • Address open CPs for the supplement
    • on the ITI CP spreadsheet, on the 'Active CPs' tab, ensure that any Assigned CPs are completed as part of the DSTU2 revision to the document, or before.
Retrieved from "http://wiki.ihe.net/index.php?title=Updates_of_Profiles_to_FHIR_DSTU2&oldid=90989"