Stream: Da+Vinci+PDex+Plan-Net
Topic: Endpoint Profile
David Clowers (Nov 02 2020 at 18:04):
Is there a working example of how the Endpoint profile should be implemented, other than the example payloads in the IG (e.g. something similar to the Heroku client reference app)? We've implemented most of the other profiles, but we're trying to understand how to best incorporate the Endpoint profile into our solution. It doesn't seem immediately obvious from the information in the IG, unless I'm missing something.
Saul Kravitz (Nov 02 2020 at 18:58):
@Robert Dieterle
Hi @David Clowers ,
The Endpoint profile may be a bit ahead of its time for Providers implementing their directories in 2020.
If all you want to do is provide the url of a website, you don't need it, since that can be provided in the telecom field (system =url).
It is intended to support, at a minimum, various types of FHIR endpoints that could be associated to a resource (basic rest, operation, messaging) and Direct messaging, as well as any other type of restful endpoint. (as enumerated http://build.fhir.org/ig/HL7/davinci-pdex-plan-net/StructureDefinition-plannet-Endpoint.html#implementation-guidance).
If you don't need it, you don't need to implement anything beyond the ability to respond to a query /Endpoint and return 0 entries.
David Clowers (Nov 02 2020 at 23:43):
@Saul Kravitz Thank you for providing this information. To confirm, if we determine that we do not need the Endpoint resource, the only requirement is to have it the Endpoint endpoint available and return an empty payload?
Saul Kravitz (Nov 04 2020 at 17:59):
@David Clowers -- that is my interpretation of the Capability Statement. You have to support the queries on Endpoint (obviously, if you have none, they will return no results), and you have to support the Endpoint profile on any endpoints you define. If you define none, then, that is an easy requirement to fulfill.
David Clowers (Nov 04 2020 at 19:05):
@Chetan Jain FYI.
Saul Kravitz (Nov 04 2020 at 23:18):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
