Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25777

Update OIDs in example messages to reflect unique concepts

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • V2 to FHIR (V2)
    • 0.2.0
    • Orders & Observations
    • Other
    • Hide

      Motion to find persuasive and review all the OIDs used (in HD, EI, EIP or wherever else so that for the same organization, facility, or application they are properly the same or different.

      Show
      Motion to find persuasive and review all the OIDs used (in HD, EI, EIP or wherever else so that for the same organization, facility, or application they are properly the same or different.
    • Hans Buitendijk / Riki Merrick: 8-0-1
    • Correction
    • Compatible, substantive

    Description

      In our example messages, anywhere there is an HD or EI or EIP data type, we should examine the namespace and OID components to ensure that anytime we have a unique namespace value that we have a unique OID. The OID can (and probably should) re-used where the namespace is the same. 

      It might be most helpful if we create a "registry" of OIDs to use in specific fields across all message examples so that we are consistent

      Attachments

        Activity

          People

            hbuitendijk Hans Buitendijk
            craig.newman Craig Newman
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: