You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: