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

us-core-12 invariant interpretation

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive
    • Specification:
      US Core (FHIR)
    • Raised in Version:
      3.1.1
    • Work Group:
      Cross-Group Projects
    • Related Artifact(s):
      USCoreImplantableDeviceProfile
    • Resolution Description:
      Hide

      Reverted previous resolution: Persuasive made 2020-10-22 00:00:00.0 with vote Brett Marquard/Craig Newman: 10-0-0//(Impact: Compatible, substantive; Category: Correction; Version: null)//Update this bullet: Implantable medical devices that have UDI information SHALL represent this information in either carrierAIDC or carrierHRF. (Note that the UDI may not be present in all scenarios such as historical implantable devices, patient reported implant information, payer reported devices, or improperly documented implants.). Server are not required to support both carrierAIDC and carrierHR.

      Remove Must Support Flags on carrierAIDC or carrierHR.

      Show
      Reverted previous resolution: Persuasive made 2020-10-22 00:00:00.0 with vote Brett Marquard/Craig Newman: 10-0-0//(Impact: Compatible, substantive; Category: Correction; Version: null)//Update this bullet: Implantable medical devices that have UDI information SHALL represent this information in either carrierAIDC or carrierHRF. (Note that the UDI may not be present in all scenarios such as historical implantable devices, patient reported implant information, payer reported devices, or improperly documented implants.). Server are not required to support both carrierAIDC and carrierHR. Remove Must Support Flags on carrierAIDC or carrierHR.
    • Resolution Vote:
      Brett Marquard/Craig Newman: 10-0-0
    • Change Category:
      Correction
    • Change Impact:
      Compatible, substantive

      Description

      The combination of Must Support flags on Device.udiCarrier.carrierAIDC, Device.udiCarrier.carrierHRF, and invariant us-core-12 is not clearly conveying the intent of only needing to provide/support a data source the HRF or the AIDC, not both.  However, the presence of the Must Support flag on both is leading Inferno to require demonstration of exposing an AIDC as well when the HRF was already exposed, or instead of an HRF.  Since the underlying system never has and AIDC that would not be possible to demonstrate lest one adds that capability for no extra value since the AIDC does not convey any further information beyond an HRF.  Documentation within the system and receipt of data from another system never result in having an AIDC value, just an HRF.  To avoid this misinterpretation we suggest to either enhance the clarity of the us-core-12 invariant, and/or provide some examples of what is expected, and consider that the must support flag is not only on individual elements, but on a set where there is no backbone element to do so.  The must support should really have been on the combination, i.e., carrier[x] is Must Support where carrierAIDC and carrierHRF are both 0..1 with the invariant on carrier[x] to ensure one of them is always present under the overall Must Support.  This may require OO to update the core resource to re-express Device.udiCarrier.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              hbuitendijk Hans Buitendijk
              Request in-person:
              Drew Torres, Hans Buitendijk
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: