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

Reference US@

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 6.1.0
    • Cross-Group Projects
    • US Core Patient Profile
    • Hide

      1) add Profile Specific Implementation Guidance to the patient profile:

      Certifying systems SHALL and non-certifyinf systems SHOULD {}follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for `Patient.address.line` and  `Patient.address.city` for new and updated records.

      • For certifying systems, this requirement does not apply to historical records/documents that are exposed through FHIR based APIs

       

      pointing to the Project US@ style guide 

      preapplied here: https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-patient.html#mandatory-and-must-support-data-elements

      2) add this Profile Specific Implementation Guidance to the RelatedPerson, Practitioner, Organization,  and  Location profiles:

      Systems  SHOULD {}follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for `Patient.address.line` and  `Patient.address.city` for new and updated records.

      3) update all examples and  inline profile "Example General" to follow style guide 

      e.g.:  Patient/example : https://build.fhir.org/ig/HL7/US-Core/Patient-example.html

       

       

      Show
      1) add Profile Specific Implementation Guidance to the patient profile: Certifying  systems SHALL and non-certifyinf  systems SHOULD { }follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for `Patient.address.line` and  `Patient.address.city` for new and updated records. For certifying systems, this requirement does not apply to historical records/documents that are exposed through FHIR based APIs   pointing to the Project US@ style guide  preapplied here: https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-patient.html#mandatory-and-must-support-data-elements 2) add this Profile Specific Implementation Guidance to the RelatedPerson, Practitioner, Organization,  and  Location profiles: S ystems   SHOULD { }follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for `Patient.address.line` and  `Patient.address.city` for new and updated records. 3) update all examples and  inline profile "Example General" to follow style guide  e.g.:  Patient/example : https://build.fhir.org/ig/HL7/US-Core/Patient-example.html    
    • Eric Haas/Brett Marquard: 16-0-0
    • Enhancement
    • Compatible, substantive
    • Yes

    Description

      USCDI v3 indicates use of US@ ([| Interoperability Standards Advisory (ISA) (healthit.gov)|https://www.healthit.gov/isa/taxonomy/term/756/uscdi-v3]), yet FHIR US Core does not reference that in the Patient profile on the .address element.  The HTI-1 proposed rule is very clear on USCDI v3 including US@ and furthermore lists the criteria that reference USCDI.  To avoid any confusion whether absence of a reference in FHIR US Core 6.1.0 implies that there is no support required for US@, propose that a statement is made that support of US@ is required, or potentially a clearly agreed to subset if appropriate to step into it.

      While this will first be considered as part of FHIR US Core 7, it should be patched into FHIR US Core 6.1.0 as this is already needed for USCDI v3 support and it would be inappropriate to encumber implementers to have to fully support FHIR US Core 7 to satisfy support for USCDI v3.  Therefore this Jira will be flagged for patching.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: