argonautproject/scheduling issues and pull requests

#68 - Appointment.RequestedPeriod should not be mandatory

Issue - State: open - Opened by brianpos over 5 years ago

#67 - Most of the links here are broken

Issue - State: open - Opened by aes1024 over 6 years ago - 1 comment

#66 - Is the 2.4.3 response body total correct?

Issue - State: closed - Opened by cooperthompson over 6 years ago - 1 comment

#65 - Do we need id properties on all the input Parameters resources?

Issue - State: closed - Opened by cooperthompson over 6 years ago - 1 comment

#64 - Example in 2.4.3 has valueDateTime as the property name for the patient-id

Issue - State: closed - Opened by cooperthompson over 6 years ago - 1 comment

#63 - Section 2.4.1 references the Hold operation instead of Book

Issue - State: closed - Opened by cooperthompson over 6 years ago - 1 comment

#62 - What is the state transition when releasing a held appt?

Issue - State: open - Opened by Healthedata1 over 6 years ago
Labels: operation$hold

#61 - How to attach other custom parameters to Slot resource

Issue - State: open - Opened by Healthedata1 over 6 years ago
Labels: PreFetch

#60 - Should appointment $find include PractitionerRole and HealthCareService

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 1 comment

#60 - Should appointment $find include PractitionerRole and HealthCareService

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 1 comment

#59 - Prefetch issues: "Smart Polling" = Subscription for change of events

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 7 comments

#59 - Prefetch issues: "Smart Polling" = Subscription for change of events

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 7 comments

#58 - Whether to add a header to Hold requests response indicating expirations

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 3 comments
Labels: operation$hold

#57 - What slot statuses to use

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 2 comments
Labels: Operation$find

#56 - review of uri type for `appt-id` parameters in $hold and $book

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 1 comment
Labels: operation$hold, operation$book

#55 - Clarify usage of location parameter in $find

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 2 comments
Labels: Operation$find

#54 - How is organization is intended to be used in operation $find

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 1 comment
Labels: Operation$find

#53 - Indication/diagnosis missing from $find operation

Issue - State: closed - Opened by cooperthompson almost 7 years ago - 2 comments
Labels: Operation$find

#52 - Using update polling for prefetching when systems don't use slots

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 4 comments
Labels: PreFetch

#51 - What is the definition of "System level trust"

Issue - State: closed - Opened by Healthedata1 almost 7 years ago - 1 comment

#50 - Should the open scheduling case use Patient$match too?

Issue - State: open - Opened by Healthedata1 about 7 years ago - 1 comment
Labels: Defer to future release

#50 - Should the open scheduling case use Patient$match too?

Issue - State: open - Opened by Healthedata1 about 7 years ago - 1 comment
Labels: Defer to future release

#49 - Should we explore providing patient details to the hold call?

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 1 comment

#48 - Can new patients use a "patient portal"?

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 1 comment
Labels: question, Patient scheduling

#47 - Whether updates or patch should be used for changes to insurance information

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 2 comments
Labels: question, Patient Registation

#46 - Issues with Coverage Resource

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 2 comments
Labels: Patient Registation

#45 - Issues with fetching slots in PreFetch Scenario

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 3 comments
Labels: PreFetch

#44 - Benefits of using Event vs Search Criteria for Pub/Sub

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 11 comments
Labels: question, Pub/Sub

#43 - Clarify Provider Based Scheduling Scope - role of EHR vs Third Part Apps

Issue - State: open - Opened by Healthedata1 about 7 years ago - 1 comment
Labels: question, Provider scheduling

#42 - Add location-reference

Issue - State: closed - Opened by cooperthompson about 7 years ago - 1 comment
Labels: Operation$find

#41 - Procedure-based scheduling support

Issue - State: open - Opened by cooperthompson about 7 years ago - 2 comments
Labels: Operation$find, Defer to future release

#40 - Need to document current vs. future pre-fetch availability

Issue - State: closed - Opened by cooperthompson about 7 years ago - 8 comments
Labels: Pub/Sub

#39 - Need to prioritize building a short list of ~10 appointment types

Issue - State: closed - Opened by cooperthompson about 7 years ago - 15 comments
Labels: Operation$find

#38 - Add urgency as an input property

Issue - State: open - Opened by cooperthompson about 7 years ago - 7 comments
Labels: Operation$find, Defer to future release

#37 - Clarity/split Appointment.$find provider property

Issue - State: closed - Opened by cooperthompson about 7 years ago - 3 comments
Labels: Operation$find

#36 - A few proposed changes for the $find parameter data types

Issue - State: closed - Opened by cooperthompson about 7 years ago - 9 comments
Labels: Operation$find, change required

#35 - Appointment/$find operation is only a resource level operation, not system level

Issue - State: closed - Opened by cooperthompson about 7 years ago - 2 comments

#34 - Should patient cancel transaction support reason

Issue - State: closed - Opened by Healthedata1 about 7 years ago - 6 comments
Labels: question, Cancel/Update/Amend

#33 - test integration with Zulip

Issue - State: closed - Opened by Healthedata1 about 7 years ago

#32 - Operations that change data should not allow GET

Issue - State: closed - Opened by daliboz over 7 years ago - 3 comments

#31 - What if anything the consumer can update in Appointment once booked?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: question, Cancel/Update/Amend

#30 - What if any server functionality do we need to document for cancelling an appointment

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: question, Cancel/Update/Amend

#29 - Do we need a separate scheduling update ('renegotiation') workflow?

Issue - State: open - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: question, Cancel/Update/Amend, Defer to future release, change required

#28 - Is patient registration in scope for this IG?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 4 comments
Labels: Patient Registation

#27 - Using a REStful update using PUT or PATCH instead of an operation

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 6 comments
Labels: operation$hold, operation$book

#26 - Should a comment parameter be added an input?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find, operation$book

#25 - If a hold operation is performed - how is the length of hold determined?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: operation$hold

#24 - Whether to use coding vs code + system for specialty and service inputs

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments

#23 - Does PractitionerRole need to be input parameter?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#22 - Should the OO be profiled?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: Operation$find

#21 - Should the output parameter Bundle be profiled?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#20 - Sprint Readiness

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Sprint 1

#19 - Does the discovery step fall into scope of Argo Scheduling?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: Discovery

#18 - Confirm that Operation$find is a resource based (and not system based) operation

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: Operation$find

#17 - QA errors

Issue - State: open - Opened by Healthedata1 over 7 years ago
Labels: IG publishing

#16 - Should there be an option for patient reference input parameter?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: Operation$find

#15 - if Max Cardinality of input >1 is a preference implied by order?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#14 - Input parameters descriptions to be clearer

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#13 - Guidance on when and how OperationOutcome should be used if more than described in FHIR.

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#12 - Do we need a spatial location input parameter?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#11 - Is the expected default behavior to return the next appointments available?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#10 - Do we need a way to limit responses?

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#9 - Consider simple parameters instead of Period so can use GET syntax

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#8 - Clarify the meaning whether >1 of an input paramater is an 'OR' or 'AND'

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#7 - What are the HTTP Error codes for the operations

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#6 - operation$find questions

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#5 - How to document when to use which parameters for each use case with an operation

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment
Labels: Operation$find

#4 - What Service and SpecialtyTerminology ( code system ) should be used

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 7 comments
Labels: Operation$find, Discovery, change required

#3 - What does the client need before they can do an availability search

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: Discovery

#2 - remove all root slice names from spreadsheets

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 1 comment

#1 - Should the server return a set of available slots vs appts

Issue - State: closed - Opened by Healthedata1 over 7 years ago - 2 comments
Labels: question

GitHub / argonautproject/scheduling issues and pull requests