medplum / medplum / 23217534358

92%

push

github

Provider: add "visit" set up after $book (#8585)

* Provider: add "visit" set up after $book

After using $book to create an Appointment and Slot resources, we end up
in a situation where we want to configure the appointment in the same
way as the older "visit" set up style. This entails selecting an
"encounter class" and a PlanDefinition, and creating a variety of
resources.

To this end, we split `createEncounter` into `createAppointment` and
`createEncounter` - the older `<CreateVisit>` code path now calls both
of these in sequence, while the newer `<AppointmentDetails>` component
that has an Appointment from a `$book` operation can call
`createEncounter` only.

This will support both the current medplum-provider $find/$book
scheduling workflow, and a future workflow where a Patient-centered app
will allow a logged in patient to create an appointment via $find/$hold.

The SchedulePage has been updated to reveal the newly created
Appointment in the Details pane after creation, allowing the provider to
immediately apply a template and create the related encounter when
appropriate.

Signed-off-by: Noah Silas <noah@medplum.com>

* PR Feedback: Error handling adjustment

Thanks @techdavidy!

Signed-off-by: Noah Silas <noah@medplum.com>

* Tighten flaky test

I think that this was sometimes finding the "Homer Simpson" entry in
both the `<Calendar>` and the `<FindPane>` components. We're explicitly
trying to test that the calendar entry is visible, so let's scope the
query to that component.

Signed-off-by: Noah Silas <noah@medplum.com>

* PR Feedback: add test case for failed encounter creation

Thanks for the suggestion Claude!

Signed-off-by: Noah Silas <noah@medplum.com>

---------

Signed-off-by: Noah Silas <noah@medplum.com>

17896 of 20323 branches covered (88.06%)

Branch coverage included in aggregate %.

32521 of 34352 relevant lines covered (94.67%)

14567.47 hits per line