Stream: Da+Vinci+PDex+Plan-Net
Topic: Pharmacy-Specific Data
David Clowers (Dec 09 2020 at 19:38):
When implementing data that is specific to pharmacies, is there a requirement to aggregate pharmacy data into the rest of the provider data, or even have them in the same instance or part of the same dataset? The reason I ask is that, for our solution, our Provider Directory and Pharmacy Directory data come from two different sources, which, for architectural reasons, makes it difficult for us to utilize the same endpoints for both. We're wondering then if we can have separate domains/endpoints for provider versus pharmacy directory in order to segregate the data, e.g.:
https://api.providersolution.net/Organization
https://api.pharmacysolution.net/Organization
David Clowers (Dec 09 2020 at 19:39):
Is there any requirement that this violates, or is this simply an implementation decision that is left up to the team to decide?
Saul Kravitz (Dec 09 2020 at 19:55):
Thoughts:
1) There would be some redundancy between the two endpoints, since InsurancePlans and Networks would need to live in both
2) Naive suggestion: Could you implement as two endpoints under the covers and just route queries to both endpoints merging the results?
My initial take is that this would be a barrier to interoperability since a client would need to know about two separate endpoints and figure out when it was supposed to query each one.
David Clowers (Dec 15 2020 at 22:12):
@Saul Kravitz Thanks, we're looking into this as a possibility. When we're trying to separate data by typical provider versus pharmacy, using Organization as an example, which one of these categories should each fall into? I'm assuming a typical provider would be either fac or prvgrp, whereas pharmacy would be atyprv.
http://build.fhir.org/ig/HL7/davinci-pdex-plan-net/ValueSet-OrgTypeVS.html
Last updated: Apr 12 2022 at 19:14 UTC
