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

need to better explain the need for all the workflow steps

    XMLWordPrintableJSON

Details

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

      Agree that the current spec needs updating. The workflow diagram has been revised and reviewed with the community, and  the documentation will be updated to match and include the rationale for the various steps. This will include noting options for sending AEOBs directly to patients that are out of scope for this IG, such as via mail, etc. if agreed upon by the community. 

      Show
      Agree that the current spec needs updating. The workflow diagram has been revised and reviewed with the community, and  the documentation will be updated to match and include the rationale for the various steps. This will include noting options for sending AEOBs directly to patients that are out of scope for this IG, such as via mail, etc. if agreed upon by the community. 
    • Rick Geimer/Paul Knapp: 9-0-1
    • Enhancement
    • Non-compatible

    Description

      This process seems to involve a lot of steps. Why can't the payer just send the AEOB to the patient when complete? Instead, the patient is notified, has to receive an access token, and then request the AEOB. If all of these steps are truly necessary, this should be better explained/justified (e.g., security concerns, etc.).

      Attachments

        Activity

          People

            rgeimer Rick Geimer
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: