Stream: argonaut
Topic: scheduling / Issue #56 review of uri type for `appt-id` p...
argo-scheduling-bot (Jan 27 2018 at 02:34):
Healthedata1 labeled Issue #56
argo-scheduling-bot (Jan 27 2018 at 02:34):
Healthedata1 labeled Issue #56
argo-scheduling-bot (Jan 27 2018 at 02:34):
Healthedata1 opened Issue #56
I think this is the most general approach since the
uritype allows for both FHIR and non FHIR endpoints. But the other options are:1 type
Referencewhich could allow for business identifiers too, but is limited to FHIR endpoints.
1. the string search parameteruriwhich is only fully specified endpoints. ( this needs further clarification in the standard since is unclear if this 'uri' is truly the same as the 'uri' type above)
argo-scheduling-bot (Jan 27 2018 at 02:39):
Healthedata1 edited Issue #56
I think this is the most general approach since the
uritype allows for both FHIR and non FHIR endpoints. But the other options are:1 type
Referencewhich could allow for business identifiers too, but is limited to FHIR endpoints.
1. the string search parameteruriwhich is only fully specified endpoints. ( this needs further clarification in the standard since is unclear if this 'uri' is truly the same as the 'uri' type above)
1. or just type 'id' since we are assuming is an appointment
argo-scheduling-bot (Mar 19 2018 at 21:53):
Healthedata1 commented on Issue #56
uri is most flexible for now
argo-scheduling-bot (Mar 19 2018 at 21:53):
Healthedata1 closed Issue #56
Last updated: Apr 12 2022 at 19:14 UTC
