Stream: Da+Vinci+PDex+Plan-Net
Topic: Health Plan API
Shamil Nizamov (Feb 05 2021 at 05:02):
The IG suggests that Health Plan API Actor: A payer publishing a directory of its provider networks through a FHIR endpoint.
Is there an example of such endpoint(s) to play with search parameters, are they publicly available at all?
Saul Kravitz (Feb 05 2021 at 18:12):
Yes, there are reference implementations:
- client: https://plan-net-client.herokuapp.com/ - type your server, or the reference server into the. 'Lookup' field and hit Lookup.
- server: https://davinci-plan-net-ri.logicahealth.org/fhir
Shamil Nizamov (Feb 05 2021 at 19:34):
Thank you! Let me explore those.
Nagarjuna Sanivarapu (Feb 07 2021 at 16:28):
@Saul Kravitz @Mark Scrimshire @Viet Nguyen @Robert Dieterle @Suma Addagadde
Based on this sample refence implementation of logica health, could you clarify on below questions.
1 ) For all provider search requests, Is the 'PractitionerRole' considered as the key primary resource? Will Location resource API be used for any of the Provider directory searches.
2) How the network information will be populated for Provider Directory and Pharmacy Directory? Our understanding is, for Pharmacy networks, it would be InsurancePlan API and for Provider its Organization with '_profile=http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Network', Is this the right understanding?
Saul Kravitz (Feb 08 2021 at 13:32):
Hi @Nagarjuna Sanivarapu
I want to be careful to distinguish between the reference implementation -- AN implementation that exercises a portion of the functionality of the plan-net IG API to serve SOME expected use cases -- and the clients and their associated queries that are supported by the plan-net IG API. The purpose of all of the SHALLs in the Plan-Net capability statement is to enable a client to be able to exercise those capabilities. So, the fact that the reference client doesn't use those capabilities does not detract from the SHALL in the IG.
For each of the use cases demonstrated by the reference client (except, inadvertently, pharmacy mix), the query used is shown at the top of the screen.
1) In the provider search (in the RI), the focal resource is PractitionerRole. Location searches could easily be part of a provider directory search, that is why they are SHALL. For example, searching for all locations associated with an organization (e.g., hospital network), or all organizations of a certain type (e.g., hospital). Searching by location (with _lastUpdated, and either all locations or by _id) would likely also be part of a clients ongoing effort to maintain an up to date picture of an evolving directory content.
2). For how to use the various profiles, please see Representing and Searching Provider Directory Data
Nagarjuna Sanivarapu (Mar 08 2021 at 15:50):
@Saul Kravitz
Hello Saul, I am trying to run Provider Client App (https://github.com/HL7-DaVinci/plan-net_client) locally with the docker, I have another postgres instance running in docker as well. I am seeing this error " Connection refused Is the server running on host "pg-hostname" (23.221.222.250) and accepting TCP/IP connections on port 5432?" . I could make connection to this DB with other DB client. I don't have much background on Ruby programming. Could you please provide additional instructions on running the client app in docker.
Thanks,
Nag
Saul Kravitz (Mar 08 2021 at 16:13):
@Dave Hill
Dave Hill (Mar 08 2021 at 16:20):
Hi @Nagarjuna Sanivarapu, I'll fire up a docker instance locally and see if I can reproduce the problem. I'll let you know.
Thanks!
Dave
Nagarjuna Sanivarapu (Mar 10 2021 at 03:05):
@Dave Hill Hello Dave, Did you get a chance to run the client locally in docker? Thanks, Nag.
Last updated: Apr 12 2022 at 19:14 UTC
