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

Requiring 5 types of clinical notes is not US foundational

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Core (FHIR)
    • 5.0.1
    • Cross-Group Projects
    • STU
    • US Core Clinical Note Type
    • Profiles and Extensions
    • 3.3 and 1.1
    • Hide

      The current US Core DocumentReference profile is focused on Clinical Notes. US Core serves more than EHRs and while Cross Group Projects/US Realm have discussed splitting US Core into a 'base' + 'core',  they have decided to only split if we get an an insurmountable number of conflicting requirements.

      The US Core editors are in conversations with the PACIO project and their PACIO-AD guide on how it fits in best with US Core. 

      Rather than adding 'not applicable', we hope to add Advance Directive guidance in a future release.

       

       

      Show
      The current US Core DocumentReference profile is focused on Clinical Notes. US Core serves more than EHRs and while Cross Group Projects/US Realm have discussed splitting US Core into a 'base' + 'core',  they have decided to only split if we get an an insurmountable number of conflicting requirements. The US Core editors are in conversations with the PACIO project and their PACIO-AD guide on how it fits in best with US Core.  Rather than adding 'not applicable', we hope to add Advance Directive guidance in a future release.    
    • Eric Haas/Jason Vogt: 12-0-0

    Description

      The intro says: "This guide and the US Core profiles have become the foundation for US Realm FHIR implementation guides. This annual release reflects changes to U.S. Core Data for Interoperability (USCDI) v3 and comments and requests from the US Realm FHIR community."  However, the Clinical Notes section requires that to be compliant with the US core document reference profile you need to support at least 5 specific note types.  In addition, several diagnostic service types.  While this is excellent for the certified EHR use case, it is not foundational to other types of US use cases that are not certified EHR centric.  One specific example is Advance Directives in which the server may be a registry of Advance Directives.  In that case the only applicable document type would be advance directive.  It seems that "not applicable" would make sense as an option.  This would allow the Advance Directive US Realm guide to build on US Core.  It feels like US Core needs a spec on top to represent the EHR specific use cases and that US Core should provide more of a foundation so as to support a variety of use cases would open up more opportunities.   

      Attachments

        Activity

          People

            Unassigned Unassigned
            vlorenzi Virginia Lorenzi
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: