Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-36712

Remove inheritance of US Core DocumentReference from ADI Profile of DocumentReference

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US PACIO Advance Directive Interoperability (FHIR)
    • 0.1.0
    • Patient Empowerment
    • PACIO ADI Document Reference [deprecated]
    • Hide
      • Remove US Core DocumentReference inheritance from Document Reference profile (PADI-DocumentReference)
      • Received approval for variance request (FHIR-38221)
      • To PADI-DocumentReference, replicate the US Core R5 constraints with the following modifications:
        • DocumentReference. type binding to PADIAdvanceDirectiveCategoriesVS (extensible)
        • DocumentReference.category slice named advance_directives with fixed value  http://loinc.org|42348-3 in place of "us-core" slice
        • DocumentReference.author 1..* MS changing US Core Patient  to must support and removing MS from US Core Practitioner
        • To definition of DocumentReference.content.attachment.data and DocumentReference.content.attachment.data add "Must Support for Data Sources means at least one of data (binary64 encoded document data) or url (location of the document) must be supported"
        • Remove all constraints from DocumentReference.context

       

      Show
      Remove US Core DocumentReference inheritance from Document Reference profile (PADI-DocumentReference) Received approval for variance request ( FHIR-38221 ) To PADI-DocumentReference, replicate the US Core R5 constraints with the following modifications: DocumentReference. type binding to PADIAdvanceDirectiveCategoriesVS (extensible) DocumentReference.category slice named advance_directives with fixed value  http://loinc.org |42348-3 in place of "us-core" slice DocumentReference.author 1..* MS changing US Core Patient  to must support and removing MS from US Core Practitioner To definition of DocumentReference.content.attachment.data and DocumentReference.content.attachment.data add "Must Support for Data Sources means at least one of data (binary64 encoded document data) or url (location of the document) must be supported" Remove all constraints from DocumentReference.context  
    • Corey Spears / Abigail Watson : 13 - 0 - 0
    • Correction
    • Non-compatible

    Description

      US Core DocumentReference requires several features including MS for ImagingStudy and Encounter. US Core will not change these requirements (https://jira.hl7.org/browse/FHIR-35759, https://jira.hl7.org/browse/FHIR-35762), so a variance request needs to be made and the inheritance should be removed. Make appropriate additions to the ADI DocumentReference profile to cover the desired constraints from the US Core profile 

      Attachments

        Activity

          People

            bmeshell Brian Meshell
            corey_spears Corey Spears
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: