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

Expand the concepts defined for DocumentReference.category

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Core (FHIR)
    • 7.0.0-ballot
    • Cross-Group Projects
    • STU
    • US Core DocumentReference Category
    • Hide

      Background

      The commenter is referring to the US Core DocumentReference Category

      which is defined as "The US Core DocumentReferences Category Value Set is a ‘starter set’ of categories supported for fetching and storing clinical notes." and includes a single concept

      Clinical-note http://hl7.org/fhir/us/core/CodeSystem/us-core-documentreference-category

       

      US Core DocumentReference Profile's Profile Specific Implementation Guidance also states:

      Although it is unclear if the commenter is proposing it, if implemented, it would be treated as a hierarchical ValueSet to include a subset of codes from the LOINC-based Document Class Value Set in the existing code.

       

      Rationale

      We recognize the value in finer-grained categories for some users. However, because there are technical complexities and challenges for implementers to support additional categories, we need to demonstrate wide adoption by the community before updating this valueset.  Note that  implementers and other guides can support other categories for their use cases.  

       

       

       

      Show
      Background The commenter is referring to the US Core DocumentReference Category which is defined as "The US Core DocumentReferences Category Value Set is a ‘starter set’ of categories supported for fetching and storing clinical notes." and includes a single concept Clinical-note http://hl7.org/fhir/us/core/CodeSystem/us-core-documentreference-category   US Core DocumentReference Profile's Profile Specific Implementation Guidance  also states: In addition to the  US Core DocumentReference Category  value set, other category schemes such as the LOINC-based  Document Class Value Set  and  IHE XDSclassCode  may be used to facilitate the sharing of health documents. Although it is unclear if the commenter is proposing it, if implemented, it would be treated as a hierarchical ValueSet to include a subset of codes from the LOINC-based Document Class Value Set in   the existing code.   Rationale We recognize the value in finer-grained categories for some users. However, because there are technical complexities and challenges for implementers to support additional categories, we need to demonstrate wide adoption by the community before updating this valueset.  Note that  implementers and other guides can support other categories for their use cases.        
    • Brett Marquard/Eric Haas: 17-0-0

    Description

      Expand the concepts defined for DocumentReference.category ( in ValueSet: US Core DocumentReference Category ) to include the most general LOINC code type for all C-CDA Clinical Note Types.

      ConsultDocumentType (2.16.840.1.113883.11.20.9.31) 11488-4
      DischargeSummaryDocumentTypeCode (2.16.840.1.113883.11.20.4.1) 18842-5
      HPDocumentType (2.16.840.1.113883.1.11.20.220) 34117-2
      ProcedureNoteDocumentTypeCode (2.16.840.1.113883.11.20.6.1) 28570-0
      ProgressNoteDocumentTypeCode (2.16.840.1.113883.11.20.8.1) 11506-3
      ReferralDocumentType (2.16.840.1.113883.1.11.20.2.3) 57133-1
      SurgicalOperationNoteDocumentTypeCode (2.16.840.1.113883.11.20.1.1) 11504-8
      TransferDocumentType (2.16.840.1.113883.1.11.20.2.4) 18761-7
      Patient Summary (proposing a new value set to encompass codes used for CCD and IPS) New LOINC code for Patient Summary

      Attachments

        Activity

          People

            Unassigned Unassigned
            LisaRNelson Lisa R. Nelson
            Lisa R. Nelson
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: