Stream: argonaut
Topic: scheduling / Issue #38 Add urgency as an input property
argo-scheduling-bot (Sep 11 2017 at 23:04):
cooperthompson opened Issue #38
Based on PA discussion, we propose adding a priority input property so that the scheduler (patient or staff) can specify if the appointment is emergency/urgent/routine.
argo-scheduling-bot (Sep 11 2017 at 23:15):
brettmarquard commented on Issue #38
Will PA create a value set in core we can reuse?
argo-scheduling-bot (Sep 12 2017 at 06:54):
brianpos commented on Issue #38
At this point I think we're letting the content be self contained in your IG until we're happy and then promote the whole thing into core.
Eric Haas (Sep 12 2017 at 21:17):
I meant there is a Appt-type valueset alread in core - not sure why need a new one?
argo-scheduling-bot (Sep 27 2017 at 00:22):
Healthedata1 commented on Issue #38
how does this differ from the appt-type parameter? These values are included see:http://build.fhir.org/ig/argonautproject/scheduling/ValueSet-types.html
argo-scheduling-bot (Sep 27 2017 at 00:22):
Healthedata1 closed Issue #38
argo-scheduling-bot (Sep 27 2017 at 00:22):
Healthedata1 reopened Issue #38
argo-scheduling-bot (Sep 27 2017 at 00:24):
Healthedata1 commented on Issue #38
Appt-type has alway seemed to conflate orthogonal concepts to me and is poorly described in all HL7 standards IMO. Although that may reflect the real world...
argo-scheduling-bot (Sep 27 2017 at 03:29):
Healthedata1 labeled Issue #38
argo-scheduling-bot (Sep 27 2017 at 21:54):
Healthedata1 commented on Issue #38
see #39
argo-scheduling-bot (Oct 10 2017 at 22:49):
Healthedata1 commented on Issue #38
Two things I need to understand regarding this issue:
Clarifying with WG is this a new element on Appt vs a new search parameter? ( and does that matter)
Clarify the Overlap of these concepts with Appt-type as implicitly defined by the Argo Scheduling Value Set:
Visit context ( e.g. Routine ) as I believe Appt-type is currently defined in FHIR resources
- vs a Service type ( e.g. Office Visit ) as I believe is commonly used in scheduling community
argo-scheduling-bot (Oct 25 2017 at 17:37):
Healthedata1 commented on Issue #38
Urgency used to prioritize Patients and "bump" decision to defer this issue to future.
argo-scheduling-bot (Oct 25 2017 at 17:37):
Healthedata1 closed Issue #38
argo-scheduling-bot (Oct 25 2017 at 17:38):
Healthedata1 reopened Issue #38
argo-scheduling-bot (Oct 25 2017 at 17:39):
Healthedata1 labeled Issue #38
Last updated: Apr 12 2022 at 19:14 UTC
