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

Inclusion of secondary anchors in events when not present in the resource

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • STU
    • Event library [deprecated]
    • Hide

      In base FHIR, a mandatory cardinality can be satisfied with the dar extension; there, the ImagingStudy-open's ImagingStudy resource can not reference a patient, despite the subject element having a cardinality of 1..1.

      In the FHIRcast DxReport-open event definition, FHIRcast mandates the presence of a patient resource in the Context table, here: https://build.fhir.org/ig/HL7/fhircast-docs/3-6-1-DiagnosticReport-open.html#context

      There is no mechanism for an implementer to not provide a patient. Practically, an a majority of implementers will require a patient. To enable this level of flexibility in the base FHIRcast spec, it becomes increasingly important for implementers to implement a "sub-IG" and not the base FHIR spec. 

      We don't currently know of any need to not provide a patient, so will not enable such behavior at this time. 

      Deferring.

      Show
      In base FHIR, a mandatory cardinality can be satisfied with the dar extension; there, the ImagingStudy-open's ImagingStudy resource can not reference a patient, despite the subject element having a cardinality of 1..1. In the FHIRcast DxReport-open event definition, FHIRcast mandates the presence of a patient resource in the Context table, here: https://build.fhir.org/ig/HL7/fhircast-docs/3-6-1-DiagnosticReport-open.html#context There is no mechanism for an implementer to not provide a patient. Practically, an a majority of implementers will require a patient. To enable this level of flexibility in the base FHIRcast spec, it becomes increasingly important for implementers to implement a "sub-IG" and not the base FHIR spec.  We don't currently know of any need to not provide a patient, so will not enable such behavior at this time.  Deferring.
    • Bas van den Heuvel / Trent Nolin: 7-0-0

    • Change Request FHIR-37096 secondary anchor in close

    Description

      A context change event can refer to another resource (e.g. encounter from imagingstudy and patient from encounter). What happens when the anchor resource does not hold the information? E.g. an ImagingStudy with not encounter reference. I suggest to only include the field when the data can be provided.

      What happens when the reference is a identifier reference?

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: