Stream: Da Vinci PDex Drug Formulary
Topic: How to scope Formulary requests for the Patient Access API
Lee Surprenant (May 06 2021 at 18:02):
I'm tryinig to understand how the Drug Formulary IG should work within the context of the Patient Access API, which is scoped to a single authenticated user.
I found https://jira.hl7.org/browse/FHIR-31073 but, unfortunately, the proposed resolution to this issue is confusing to me and I believe that it inadequately addresses the issue.
image.png
Lee Surprenant (May 06 2021 at 18:03):
Specifically, I do not understand the concept of "plan selection" in this table.
How do we get from a single patient context (provided via SMART App Launch) to a list of plans for the user to perform this selection?
Lee Surprenant (May 06 2021 at 18:05):
We were thinking that this could be done by linking a CARIN for BlueButton Coverage resource (with type DRUGPOL or HIP or similar) to a Drug Formulary "Formulary Coverage Plan", either explicitly through an extension of type Reference or implicitly through an identifier that would match the PlanId that is used in both the "Formulary Coverage Plan" List.identifier and the Formulary Drug MedicationKnowledge.usdf-PlanId-extension.
If such linkage was explicitly prescribed, it would be possible for both clients and servers to:
- obtain a list of active Coverage resources for a single patient
- either allow the end user to select a particular plan or scope all requests to the member's active plan(s)
Dave Hill (May 07 2021 at 15:11):
@Lee Surprenant Using the Coverage resource to connect to the Formulary CoveragePlan is what we were thinking as well. We can potentially discuss this further during today's PDex call.
Dave Hill (May 07 2021 at 15:42):
@Corey Spears
Bryan Briegel (May 07 2021 at 18:45):
Copying over to thread the notes as recorded from today's PDex call:
Q: Formulary - Once a patient logs in, how do we connect them to their formulary?
R: Options:
Through PDex coverage resource, then an internal mapping to get them to the appropriate coverage and coverage plan.
Behind the scenes internal mapping (outside FHIR) - then you wont have the dependency between coverage plan and coverage resource.
can also be one prescription drug plan offered to members, no choice, so just return the single drug plan. @Dave Hill @Lee Surprenant @Corey Spears
Lee Surprenant (May 07 2021 at 18:55):
Thanks Bryan. It still seems to me that we'd want to have some way to link a member's Coverage resource to its corresponding Formulary Coverage Plan and that there ought to be a recommended way for doing that.
Assuming you wanted to link a PDex Coverage (assuming that is http://hl7.org/fhir/us/davinci-pdex/StructureDefinition-hrex-coverage.html ?) to a Formulary Coverage Plan, which field would you use for that?
Last updated: Apr 12 2022 at 19:14 UTC
