DocumentReference doesn't need to support data and URL

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • 3.2.0 [deprecated]
    • Cross-Group Projects
    • US Core DocumentReference Profile
    • Profiles and Extensions
    • Hide

      DocumentReference.content.attachment.url or DocumentReference.content.attachment.data or both SHALL be present.

      Systems are not required to support both DocumentReference.content.attachment.url AND DocumentReference.content.attachment.data

      Make it clear although both marked MUST SUPPORT, systems may chose to only support one.

      Will model after language in Implantable Devices:

      Although both are marked as must support, the server systems are not required to support both carrierAIDC and carrierHRF, but SHALL support at least one of these elements.

      Show
      DocumentReference.content.attachment.url or DocumentReference.content.attachment.data or both SHALL be present. Systems are not required to support both DocumentReference.content.attachment.url AND DocumentReference.content.attachment.data Make it clear although both marked MUST SUPPORT, systems may chose to only support one. Will model after language in Implantable Devices: Although both are marked as must support, the server systems are not required to support both carrierAIDC and carrierHRF, but SHALL support at least one of these elements.
    • Brett Marquard/Eric Haas: 17-0-3
    • Clarification
    • Compatible, substantive

      Data and URL both do not need to be must support. Our server only returns a binary URL and not the data inline. Having data be must support would require us to prove that we return data that way.

            Assignee:
            Unassigned
            Reporter:
            Andrew Torres
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: