Stream: Da Vinci PDex Drug Formulary
Topic: API
Bapi Behera (Jun 16 2020 at 18:22):
In the IG "DaVinci Payer Data Exchange US Drug Formulary" we have 2 resources "List" and "MedicationKnowledge". Do we need to create 2 separate API?
In the search criteria, the URL has the resource Name. Does it mean that API should have the resource name
-
the URL has "/List"
GET [base]/List?_profile=http://hl7.org/fhir/us/davinci-drug-formulary/StructureDefinition/usdf-CoveragePlan -
The URL has "MedicationKnowledge"
GET [base]/MedicationKnowledge?_profile=http://hl7.org/fhir/us/davinci-drug-formulary/StructureDefinition/usdf-FormularyDrug&DrugPlan=myPlanID
Lloyd McKenzie (Jun 16 2020 at 18:25):
In FHIR terms, that's generally considered a single API, but yes, you'll need each endpoint. You'll also need /meta - which is a requirement for all FHIR servers.
Bapi Behera (Jun 16 2020 at 18:30):
So we should have the 2 separate endpoint - One for List & One for MedicationKnowledge. There is already a base medicationKnowledge endpint API. How the IG MedicationKnowlege will be implemented?
Lloyd McKenzie (Jun 16 2020 at 18:47):
I don't understand your question - what do you mean by IG MedicationKnowledge? (Also, as mentioned there will be 3 endpoints - /meta, /List and /MedicationKnowledge)
Bapi Behera (Jun 25 2020 at 18:22):
In the IG "DaVinci Payer Data Exchange US Drug Formulary" we have 2 resources "List" and "MedicationKnowledge". Per IG, there are 2 endpoints. I am wondering why 2 separate endpoints? We could have just one endpoint with _include medication knowledge as an option.
"/List"
GET [base]/List?_profile=http://hl7.org/fhir/us/davinci-drug-formulary/StructureDefinition/usdf-CoveragePlan
Last updated: Apr 12 2022 at 19:14 UTC
