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

Add guidance for support of Bulk Data export for shopping experience

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Da Vinci Drug Formulary (FHIR)
    • 1.0.1
    • Pharmacy
    • Use Cases and Overview
    • Hide

      Add Guidance that a server may support bulk data.

       

      A server MAY support Bulk Data IG for the retrieval of formulary data not related to an individual. The Bulk Data IG may be used because the data set for formularies could be large as a server may manage multiple formularies, each of which may contain thousands of drugs. If and how authorization is supported is not defined by this specification, however, the Bulk IG does provide guidance on SMART Backend Service Authorization.

      If a Formulary server supports the Bulk Data IG:

      • The server SHOULD support the system level export operation [base]/$export.
      • The server SHOULD support InsurancePlanBasicMedicationKnowledge, and Location resource types for the [base]/$export?_type.
      • The server SHOULD return only formulary related resources conformant to this guide.
      • The server SHOULD support the Bulk Data Kick-off Request.
      • The server SHOULD support the Bulk Data File Request.
      • The server MAY support the Bulk Data Status Request.
      • The server MAY support the Bulk Data Delete Request.

      Add Draft Graph Definitions for expected returned results:

      • usdf-PayerInsurancePlanBulkDataGraphDefinition
      • usdf-FormularyBulkDataGraphDefinition
      Show
      Add Guidance that a server may support bulk data.   A server  MAY  support  Bulk Data IG  for the retrieval of formulary data not related to an individual. The Bulk Data IG may be used because the data set for formularies could be large as a server may manage multiple formularies, each of which may contain thousands of drugs. If and how authorization is supported is not defined by this specification, however, the Bulk IG does provide guidance on SMART Backend Service Authorization. If a Formulary server supports the Bulk Data IG: The server  SHOULD  support the system level export operation  [base] /$export . The server  SHOULD  support  InsurancePlan ,  Basic ,  MedicationKnowledge , and  Location  resource types for the  [base] /$export?_type . The server  SHOULD  return only formulary related resources conformant to this guide. The server  SHOULD  support the Bulk Data Kick-off Request. The server  SHOULD  support the Bulk Data File Request. The server  MAY  support the Bulk Data Status Request. The server  MAY  support the Bulk Data Delete Request. Add Draft Graph Definitions for expected returned results: usdf-PayerInsurancePlanBulkDataGraphDefinition usdf-FormularyBulkDataGraphDefinition
    • Scott Robertson / Corey Spears : 14-0-1
    • Enhancement
    • Non-substantive

    Description

      Shopping experience may involve an individual directly searching for a plan directly with a payer/PBM, but it could also include third parties that are providing cross plan comparison. Cross plan shopping might be better addressed through a bulk download capability.

      Attachments

        Activity

          People

            Unassigned Unassigned
            corey_spears Corey Spears
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: