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

Make a stronger case as to why FHIR is the best

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Da Vinci Patient Cost Transparency (PCT) (FHIR)
    • 0.1.0 [deprecated]
    • Financial Mgmt
    • STU
    • Use Case and Actors
    • Hide

      Add to the Overview section (before the line with the acronyms link):

       
      By using the FHIR standard and implementing this guide, providers and payers can enhance their existing technologies, where applicable, for estimating patient costs securely and efficiently using common open web technologies. The anticipated benefit of using FHIR APIs is to enable applications of the Patients’ choice to give greater transparency into patient-specific estimated costs of expected healthcare services and items.
       FHIR is being used for consumer access to healthcare related data at significant scale today, and there are regulatory requirements in the form of the CMS Patient Access API for FHIR support for the related use case of post adjudicated claims. Use of an aligned FHIR standard would keep the barrier to consumer adoption relatively low.
       

      Show
      Add to the Overview section (before the line with the acronyms link):   By using the FHIR standard and implementing this guide, providers and payers can enhance their existing technologies, where applicable, for estimating patient costs securely and efficiently using common open web technologies. The anticipated benefit of using FHIR APIs is to enable applications of the Patients’ choice to give greater transparency into patient-specific estimated costs of expected healthcare services and items.  FHIR is being used for consumer access to healthcare related data at significant scale today, and there are regulatory requirements in the form of the CMS Patient Access API for FHIR support for the related use case of post adjudicated claims. Use of an aligned FHIR standard would keep the barrier to consumer adoption relatively low.  
    • Corey Spears / Rachel Foerster : 14-0-0
    • Clarification
    • Non-substantive

    Description

      In response to the note ". Note: Translating the GFE bundle to X12 or any other format is not required to be conformant with this IG." We would like to stress that there should be standardized FHIR to X12 mapping...This comment also begs the question of the ROI if stakeholders are going to need to translate from FHIR to X12 – which increases costs and the chance of errors. Suggest that the guide make a stronger case of why FHIR should be used for the GFE/AEOB process.

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: