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

Use Cases should include an example of a payer sending USCDI info to a physician.

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Highest
    • Resolution: Not Persuasive with Modification
    • US Core (FHIR)
    • 3.1.1
    • Cross-Group Projects
    • Basic Provenance
    • 2.2
    • Hide

       Within the family of FHIR HL7 IGs this use case is covered.  The particular use you are describing is covered in Da Vinci PDEX with depends upon US Core. 

      Will add the following text to section 1.3 to clarify that the actors are not limited to those presented in the examples.

      The terms "US Core Requestor" and "Client"  are used interchangeably throughout this guide and we don’t mean to limit ourselves to only patient and provider apps, the same technology can be used by payers and other users. Please read “Client” here as a short-hand notation for something like “user application”

      The terms "US Core Responder" and "Server" and "EHR" are used interchangeably throughout this guide and we don’t mean to limit ourselves to electronic health record systems.  The same technology can be used in HIEs, care coordination platforms, population health systems, etc. Please read "Server" or “EHR” as a short-hand notation for something like “interoperable healthcare platform”

      Show
       Within the family of FHIR HL7 IGs this use case is covered.  The particular use you are describing is covered in Da Vinci PDEX with depends upon US Core.  Will add the following text to section 1.3 to clarify that the actors are not limited to those presented in the examples. The terms " US Core Requestor " and "Client"  are   used interchangeably throughout this guide and   we don’t mean to limit ourselves to only patient and provider apps, the same technology can be used by payers and other users. Please read “Client” here as a short-hand notation for something like “user application” The terms " US Core Responder" and "Server" and "EHR" are   used interchangeably throughout this guide and we don’t mean to limit ourselves to electronic health record systems.  The same technology can be used in HIEs, care coordination platforms, population health systems, etc. Please read "Server" or “EHR” as a short-hand notation for something like “interoperable healthcare platform”
    • Brett Marquard/Eric Haas:12-0-0
    • Enhancement
    • Non-substantive

    Description

      This section should include a use case/example of a payer sending USCDI info to a physician. For example, payers using APIs to enable the sending of patient claims, encounter data and clinical data directly to physician's EHRs allowing for physicians to have their patients’ complete medical history.

      Existing Wording:

      Use Cases

      (Comment 18 - imported by: Jean Duteau)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              molly.malavey@ama-assn.org Molly Reese
              Molly Reese
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: