Stream: implementers
Topic: Specifying a referral page for a HealthcareService
Tim Berezny (Aug 18 2020 at 14:07):
I have (at least) two URLs I want to share about a HealthcareService
- the service's marketing webpage
- the service's referral/contact page
I think that the marketing page belongs at HealthcareService.telecom.url. Should I create an extension for the referral page? I was wondering if there's also a way to use HealthcareService.telecom.url with slicing but I don't know what i'd use as the discriminator.
David Pyke (Aug 18 2020 at 14:19):
Since HealthcareService uses ContactPoint that uses a simple string for value, you could add "marketing" and "referral" to the use codelist and then slice on that, putting the URL in value.
Vassil Peytchev (Aug 18 2020 at 14:21):
HealthcareService.endpoint has some hints that it could be used somehow for this purpose. Unfortunately HealthcareService.telecom.use has a required binding... Maybe some kind of extension on telecom?
David Pyke (Aug 18 2020 at 14:29):
You're right, I misread the binding. Then yes, likely needs an extension because endpoint is designed around interop, not marketing.
Tim Berezny (Aug 18 2020 at 14:38):
Using Endpoint is an interesting idea. I guess I would create it with a HealthcareSerivce.endpoint>connectionType.code=referral-page, would that make sense?
Similarly, I want to publish what a services SMART on FHIR url would be, I think I could do this same thing with HealthcareSerivce.endpoint>connectionType.code=sof-referral-page.
Would that make sense?
Vassil Peytchev (Aug 18 2020 at 14:49):
The sof-referral page seems appropriate for an endpoint, but as David pointed out, my initial suggestion for referral contact page doesn't match the intent of the resource (I was skimming the references for directory entries).
Tim Berezny (Aug 18 2020 at 14:51):
Yes that makes sense to me. So extension for public referral page, endpoint for sof launch page sounds like a good idea. Thanks for the feedback.
Last updated: Apr 12 2022 at 19:14 UTC
