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

Define server requirements for Choice of Profile Elements scenario

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive
    • US Core (FHIR)
    • 3.2.0
    • Cross-Group Projects
    • General Guidance
    • 5.4.6
    • Hide

      update   http://build.fhir.org/ig/HL7/US-Core/conformance-expectations.html#must-support---choice-of-profile-elements to: 

       

      There are several instances in this Guide where there is a choice of supporting one or another profile element to meet the must support requirement.  In such instances, the server SHALL support at least one such element, and the client application SHALL support all such elements. There is no way to define this in a computable way, but these instances are clearly documented in the Profile specific implementation guidance sections

      For example:

      • US Core Medication Request Profile - The MedicationRequest resource can represent that information is from a secondary source using either a boolean flag or reference in MedicationRequest.reportedBoolean, or a reference using MedicationRequest.reportedReference to Practitioner or other resource. Although both are marked as must support, servers are not required to support both a boolean and a reference, but SHALL choose to support at least one of these elements.
      Show
      update    http://build.fhir.org/ig/HL7/US-Core/conformance-expectations.html#must-support---choice-of-profile-elements to:    There are several instances in this Guide where there is a choice of supporting one or another profile element to meet the must support requirement.  In such instances, the server SHALL support at least one such element, and the client application SHALL support all such elements. There is no way to define this in a computable way, but these instances are clearly documented in the Profile specific implementation guidance sections For example: US Core Medication Request Profile  - The MedicationRequest resource can represent that information is from a secondary source using either a boolean flag or reference in  MedicationRequest.reportedBoolean , or a reference using  MedicationRequest.reportedReference  to Practitioner or other resource. Although both are marked as must support, servers are not required to support both a boolean and a reference, but  SHALL  choose to support  at least one  of these elements.
    • Brett Marquard/Gay Dolin: 11-0-0
    • Clarification
    • Non-substantive

    Description

      Recommend adding sentences up front describe server and client expectations, before providing examples.  Recommended rewording below to be used prior to examples - remove current text after samples:

      There are several instances in this Guide where there is a choice of supporting one or another profile element to meet the must support requirement.  In such instances, the server SHALL support at least one such element, and the client application SHALL support all such elements. There is no way to define this in a computable way, but these instances are clearly documented.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Russell Ott Russell Ott
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: