Stream: implementers
Topic: Endpoints for plain URLs
Abbie Watson (Jul 31 2020 at 17:41):
Is it appropriate to use an Endpoint resource for plain public-facing URLs? It seems that connectionTypeand payloadType are required, but the associated value sets don't contain null values for non-FHIRized urls. It would be nice to be able to associate a vanilla website/homepage with a Location, and the reference to Endpoint almost satisfies that usecase.
Would the recommended approach be to put the URL in the Location.endpoint.reference? In the Location.meta somewhere? In the Endpoint.address but not specify the connectionType/payloadType? Or create an adhoc system for connectionType/payloadType? Or just go ahead and create falsy values for connectionType/payloadType?
Lloyd McKenzie (Jul 31 2020 at 20:22):
@Brian Postlethwaite
Brian Postlethwaite (Aug 01 2020 at 07:02):
Wouldn't that just go location.contact?
Abbie Watson (Aug 02 2020 at 05:57):
D'oh. Didn't think of that. Obvious approach right there in the spec. That works perfect. Thanks for the sanity check.
Last updated: Apr 12 2022 at 19:14 UTC
