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

Specimen resource query expectations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • US Core Specimen Profile
    • Capability Statements
      Profiles and Extensions
    • 13.146.1
    • Hide

      Rationale

       
      Overall, the "_include" capabilities could provide significant benefits to the FHIR US Core implementation, including improved efficiency, interoperability, data consistency, and user experience.

      But careful consideration needs to be given to compatibility with other profiles before formally adding support for the "_include" capabilities to US Core. Adding an "_include" capability to US Core is done by including the "_include" parameter in the list of supported parameters for the source resource in the CapabilityStatement. For example, adding an "_include specimen" capability impacts compatibility with other US Core Observation profiles, which do not require the specimen element but share the resource-wide search parameters and Quick Start documentation. Therefore, the reader would need to understand that specific search parameters apply only to certain profiles making it more difficult for developers to understand and implement. This can lead to longer development time and higher costs.

      For this reason, we have limited this as guidance in the target US Core Specimen Profile.
       

      Proposal

       
      Add guidance and an example query to the Specimen Quick Start Section.
       
       

       
      Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses and the information provided is based on our experience and implementer feedback and our design choices for US Core.

      Show
      Rationale   Overall, the "_include" capabilities could provide significant benefits to the FHIR US Core implementation, including improved efficiency, interoperability, data consistency, and user experience. But careful consideration needs to be given to compatibility with other profiles before formally adding support for the "_include" capabilities to US Core. Adding an "_include" capability to US Core is done by including the "_include" parameter in the list of supported parameters for the source resource in the CapabilityStatement. For example, adding an "_include specimen" capability impacts compatibility with other US Core Observation profiles, which do not require the specimen element but share the resource-wide search parameters and Quick Start documentation. Therefore, the reader would need to understand that specific search parameters apply only to certain profiles making it more difficult for developers to understand and implement. This can lead to longer development time and higher costs. For this reason, we have limited this as guidance in the target US Core Specimen Profile.   Proposal   Add guidance and an example query to the Specimen Quick Start Section.       Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses and the information provided is based on our experience and implementer feedback and our design choices for US Core.
    • Brett Marquard / Jason Vogt : 16-0-1
    • Clarification
    • Non-substantive

    Description

      "Queries on the Specimen resource are expected to be within the context of an Observation or DiagnosticReport resource query."

       

      Please add Supported _includes for Observation to support this - http://hl7.org/fhir/us/core/2023Jan/CapabilityStatement-us-core-server.html#resource-details

       

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            emmanurse Emma Jones
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: