medplum / medplum / 23914850865

92%

main: 92%

push

github

Teach scheduling operations to use HealthcareService scheduling parameters (#8580)

* Clean up required service-type parameter types

In commit b98f2b0551 this went from optional to required, but I missed
this opportunity to tidy up the types. Oops! Let's correct that.

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

* Teach $find operation to use ActivityDefinition scheduling parameters

When setting up scheduling for multiple providers, we want to be able to
set the SchedulingParameters up in a single place and have it be shared
across other resources, so that we don't have to keep many Schedule
extensions in sync.

To that end, you may define these parameters on an ActivityDefinition
whose `code` attribute matches the `serviceType` value in the scheduling
parameters.

This has some extra priority rules that we must follow:

- If a Schedule has any extensions exactly matching a requested service
  type, only those extensions are used. This lets an individual calendar
  override the shared rules.

- Next, any extensions from an ActivityDefinition that match a requested
  service type are used.

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

* Teach $book operation to use ActivityDefinition scheduling parameters

When setting up scheduling for multiple providers, we want to be able to
set the SchedulingParameters up in a single place and have it be shared
across other resources, so that we don't have to keep many Schedule
extensions in sync.

In the parent commit we implemented this in the $find operation. Here we
hoist some of the helpers authored there so they can be shared with
$book, and then start using them.

We perform a little bit of extra checking in $book (filtering the
returned scheduling parameters based on attributes like `duration` in
comparison to the slot requested).

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

* Feedback: prefer `getReferenceString` over `Reference.reference` access

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

* Shar... (continued)

18016 of 20453 branches covered (88.08%)

Branch coverage included in aggregate %.

59 of 59 new or added lines in 3 files covered. (100.0%)

32690 of 34530 relevant lines covered (94.67%)

14519.77 hits per line