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

don't assign meaning to specific ordinals in array

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Sync error event [deprecated]
    • Hide

      We will remove the implication / requirement that specific ordinals have specific meaning in OperationOutcome.issue.details.coding, and instead continue to mandate the coding's sytem, and encourage implementers to examine the system value to determine the meaning of the code. 

      Note that this change reverts a change made since ballot. 


      Technically this will be done by defining a profile on OperationOutcome with a slice that holds the restrictions

      Show
      We will remove the implication / requirement that specific ordinals have specific meaning in OperationOutcome.issue.details.coding, and instead continue to mandate the coding's sytem, and encourage implementers to examine the system value to determine the meaning of the code.  Note that this change reverts a change made since ballot.  Technically this will be done by defining a profile on OperationOutcome with a slice that holds the restrictions
    • Eric Martin/Catie Ladd: 4-0-0
    • Correction
    • Non-compatible

      In syncerror: https://build.fhir.org/ig/HL7/fhircast-docs/3-2-1-SyncError.html, we imply that specific ordinals in the OperationOutcome.details array have specific meaning. 

      Instead, implementers should look to the system of the  coding to determine the meaning of the OperationOutcome.details.coding[x].code.

       

            bvdh Bas van den Heuvel
            Isaac.Vetter Isaac Vetter
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: