FHIR Chat · Exposing patient access endpoints · Da+Vinci+PDex+Plan-Net

Stream: Da+Vinci+PDex+Plan-Net

Topic: Exposing patient access endpoints

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:31):

As part of the hackathon for DevDays last week, I spent some time thinking about whether/how the provider directory APIs could help patients/members select a provider that supports health information exchange.
I opened a thread on the patient empowerment stream and also contacted Saul about whether/how the Provider Directory IG supports this.

This response in particular made me think that the IG should probably be more clear about the proper code to use for "patient access" endpoints:
https://chat.fhir.org/#narrow/stream/179262-patient-empowerment/topic/Suggesting.20new.20extensions.20for.20provider.20directories/near/201390901

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:38):

I wanted to capture (and confirm) Saul's response here for improved visibility; he suggested that a patient access endpoint (e.g. one that supports CARIN BB) would be one in which

  • Endpoint.connectionType = hl7-fhir-rest
  • Endpoint.extension.usecase has type treatment; and
  • Endpoint.extension.usecase points to the implementation guide being supported

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:40):

for the implementation guide pointer, I'm wondering if that should be clarified to specifically indicate that the url should match the canonical uri for the target implementation guide. so, for CARIN BB, that would be http://hl7.org/fhir/us/carin-bb/ImplementationGuide/carin-bb

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:41):

i also wonder if that extension value should be of type "canonical" instead of just a uri; that way it could reference the specific version of the implementation guide being supported

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:42):

for example: http://hl7.org/fhir/us/carin-bb/ImplementationGuide/carin-bb|1.0

view this post on Zulip Lee Surprenant (Jun 22 2020 at 14:44):

and, finally, for the Endpoint.extension.usecase "Type" code, I'm wondering if there should be some code value other than treatment. these patient access endpoints are already out there (and hopefully getting more common) and so maybe this use case deserves its own dedicated code in the valueset?

view this post on Zulip Saul Kravitz (Jul 01 2020 at 17:04):

Thanks Lee.
Endpoint.extension.usecase.extension.type is currently bound to a VS from codesystem http://hl7.org/fhir/R4/v3/ActReason/cs.html ... See anything else in there that would be appropriate?
Endpoint.extension.usecase.extension.Standard is of type 'uri'. Replacing with 'canonical', or allowing uri or canonical makes sense to me.

@Robert Dieterle Thoughts?

view this post on Zulip Lee Surprenant (Jul 01 2020 at 17:22):

See anything else in there that would be appropriate?

PATRQT (which is already in your valueset) might be the closest, but even that one seems to imply something more than just "give the patient access to their data"...but maybe folks can just key off the IG uri instead

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -