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

Defining how access to an authenticated Formulary works

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci Drug Formulary (FHIR)
    • 1.0.1
    • Pharmacy
    • Formulary Coverage Plan [deprecated]
      Formulary Drug
    • (many)
    • Hide

      The following table describes the behavior of the API response across provided parameters and the current state of the member (plan selected or not, in group or not).  This table and explanations would be added to the IG to more clearly describe how the authenticated formulary endpoint behaves.

      Show
      The following table describes the behavior of the API response across provided parameters and the current state of the member (plan selected or not, in group or not).  This table and explanations would be added to the IG to more clearly describe how the authenticated formulary endpoint behaves.
    • Melva Peters / Dave Hill : 13-0-0
    • Enhancement
    • Compatible, substantive

    Description

      The STU1 (and 1.0.1) IG anticipates open access to a Formulary Endpoint.
      The CMS Interop Rule includes Formulary as part of the PatientAccess API, with authenticated access.   One might infer that when a member is authenticated, they would see "their" CoveragePlan, and its associated FormularyDrugs only. 

      How does this work?
      Are the search parameters constrained following authentication so that PlanID is set to the member's plan?
      What is the impact on other issues (specifically, having the cardinality of plan-specific information in FormularyDrug grow from 1..1)?   

      Attachments

        1. image-2021-03-31-16-49-58-905.png
          image-2021-03-31-16-49-58-905.png
          242 kB

        Activity

          People

            Unassigned Unassigned
            saul_kravitz Saul Kravitz
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: