Stream: implementers
Topic: Provider Directory and "Service Discovery"
Gunther Meyer (Apr 08 2016 at 12:50):
Hi All!
Gunther Meyer (Apr 08 2016 at 12:59):
I recently attended the ONC Provider Directory, and Brian mentioned that the work on the Provider Registry Implementation Guide has started.
I was wondering if we could use the Provider Registry to store API information.
The Use Cases would be something like the following:
As a patient I want to connect to my Doctor’s Hospitals’ or Clinic’s or Practice’s EHR’s API using a mobile app, knowing only my provider’s name and maybe practice/hospital.
One example of this could be the Sync 4 Science initiative in the USA.
The patient or user could find their provider and org, and from there an App could pick up the URL of, so, the conformance statement.
Regards
Gunther
Brian Postlethwaite (Apr 11 2016 at 01:04):
This is something that we'd like to consider the directory resources could handle, and there is a new resource proposal in the continuous build that is the intiial draft of the endpoint resource to be considered. (Very draft)
Brian Postlethwaite (Apr 11 2016 at 01:04):
http://hl7-fhir.github.io/endpoint.html
Brian Postlethwaite (Apr 11 2016 at 01:05):
This is not currently linked from any indexes as yet either.
Gunther Meyer (Apr 11 2016 at 12:14):
Thanks for sharing Brian, going through it now.
Brian Postlethwaite (Apr 12 2016 at 05:32):
Jeff from MiHN has had a quick look also and noted that there are some minor differences to their definition which I plan to review and incorporate.
Brian Postlethwaite (Apr 12 2016 at 05:32):
(They have an extension on basic to create a DSTU2 conformance resource for this)
Gunther Meyer (Apr 12 2016 at 12:37):
So I think the area that is least defined, but probably will require some prototyping to test out the variability, is payload (type and format).
I think ii mixes the concepts of purpose (why would you use the endpoint) with a definition of what is passed in and what is returned.
I think we can define purpose well. Definition of parameters sounds more like conformance or definition of meta-programming to me, and if that is the case I'd suggest defer it.
e.g. Some codified way of saying
'This is a Careplan CCDA Document and you need to use XDS.b to retrieve it' makes sense
Also, Public Key seems to require some additional information, such as the purpose of the key
Last updated: Apr 12 2022 at 19:14 UTC
