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

Need to provide some guidance when specific code systems are to be used in ServiceRequest

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Not Persuasive with Modification
    • US Core (FHIR)
    • 4.1.0
    • Cross-Group Projects
    • STU
    • Terminology
    • Hide

      Background:

      This IG is unique because it describes a foundational set of profiles and associated FHIR Search API. Although this IG provide general guidances over select use cases, These use case are driven by USCDI requirements. For example see the SDOH Guidance for more information when exchanging Social Determinants of Health (SDOH) Service Requests. Nevertheless, the profiles are intended to be used by implementers and IG developers over a broad set of domains and use cases. To allow for this reuse the profiles set the minimum expectation for recording, searching, and fetching and thus contain few required elements and use broad or loosely bound terminologies. The expectation is that the implementer or implementation community will further constrain the US Profile for their particular use case, including limiting the terminology to what is appropriate for their domain.

      Reasoning:

      We acknowledge that the ServiceRequest valueset is broad to accommodate a broad set of use cases. However the topic of lab orders is out of scope for this version of US Core and the general expectation is that the implementer or implementation community will further constrain it for their particular domains such as laboratory.
       

      Proposed Changes:

      Add an implementation note to ServiceRequest Implementation Notes Section:

      • The `ServiceRequest.code` valueset is broad to accommodate a wide variety of use cases and should be constrained to a subset for a particular use case or domain. (for example, LOINC for laboratory orders.)
      Show
      Background: This IG is unique because it describes a foundational set of profiles and associated FHIR Search API. Although this IG provide general guidances over select use cases, These use case are driven by USCDI requirements. For example see the SDOH Guidance for more information when exchanging Social Determinants of Health (SDOH) Service Requests. Nevertheless, the profiles are intended to be used by implementers and IG developers over a broad set of domains and use cases. To allow for this reuse the profiles set the minimum expectation for recording, searching, and fetching and thus contain few required elements and use broad or loosely bound terminologies. The expectation is that the implementer or implementation community will further constrain the US Profile for their particular use case, including limiting the terminology to what is appropriate for their domain. Reasoning: We acknowledge that the ServiceRequest valueset is broad to accommodate a broad set of use cases. However the topic of lab orders is out of scope for this version of US Core and the general expectation is that the implementer or implementation community will further constrain it for their particular domains such as laboratory.   Proposed Changes: Add an implementation note to ServiceRequest Implementation Notes Section: The `ServiceRequest.code` valueset is broad to accommodate a wide variety of use cases and should be constrained to a subset for a particular use case or domain. (for example, LOINC for laboratory orders.)
    • Brett Marquard/Eric Haas: 15-0-0
    • Clarification
    • Non-substantive

    Description

      This value set draws from many different code systems, because it supports different domains. within each domain more guidance should be given as to what codes are expected to be used - for example ServiceRequest for lab tests SHALL use LOINC when available - though folks may argue SNOMED CT could also be used (but NOT with the contstrained set proposed here)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              RikiM Ulrike Merrick
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: