Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

discovery of fhir endpoint for a recipient #42

Open
JohnMoehrke opened this issue Sep 15, 2021 · 2 comments
Open

discovery of fhir endpoint for a recipient #42

JohnMoehrke opened this issue Sep 15, 2021 · 2 comments

Comments

@JohnMoehrke
Copy link
Collaborator

given the initial patient corrections communication would be addressed to .recipient, which likely is not more specific than Organization but might somehow be more specific,
when submitting the communication one needs a FHIR end point (URL)
then use other defined directory lookup implementation guides such as vhDir

Where these directory IG already have solutions for finding the FHIR end point (URL) given various ways to lookup. Such as starting with simply an organization name.

on the connectathon call this was the approach to recommend

@JohnMoehrke JohnMoehrke self-assigned this Sep 15, 2021
@JohnMoehrke
Copy link
Collaborator Author

Lisa chats

Is this a useful statement? All communications are processed through the digital endpoint designated by the organization as the API endpoint used for handling medical record corrections. How a client application finds out what endpoint an organization uses for their medical record correction API is out of scope for this IG. One option would be to look up the organization's digital endpoint for this purpose in an online directory service such as that specified by VhDIR.

@JohnMoehrke JohnMoehrke removed their assignment Mar 30, 2022
@JohnMoehrke
Copy link
Collaborator Author

I removed assignment from me. I am not sure if this is still an issue to be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant