medplum / medplum / 22237055927

92%

main: 92%

push

github

Support instance-level custom operations with resource input (#8477)

* feat(fhir): pass resource as event.input for instance-level custom operations

When a custom FHIR operation is invoked with a specific resource ID
(e.g. POST /fhir/R4/Patient/:id/$my-custom-operation), the target
resource is now automatically fetched and passed as event.input to
the bot, instead of passing the raw request body.

System-level and type-level operations (no resource ID in the URL)
continue to use the request body (POST) or query string (GET) as input.

https://claude.ai/code/session_01SWTtcyqQ9JvVP6Snuf1Ki1
Signed-off-by: Rahul Agarwal <rahul@medplum.com>

* chore: update package-lock.json after npm install

https://claude.ai/code/session_01SWTtcyqQ9JvVP6Snuf1Ki1
Signed-off-by: Rahul Agarwal <rahul@medplum.com>

* fix(fhir): only use instance resource as input when operation.instance is true

Gate the automatic resource loading for instance-level custom operations
behind the `operation.instance` flag in the OperationDefinition, ensuring
the URL structure alone doesn't trigger instance-level behavior for
type-level or system-level operations.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Rahul Agarwal <rahul@medplum.com>

* Revert package-lock.json

Signed-off-by: Cody Ebberson <cody@ebberson.com>

* test(fhir): add comprehensive tests for instance-level custom operations

Added three test cases to cover edge cases and ensure proper behavior:
- Verify 404 return when instance-level operation targets non-existent resource
- Confirm GET requests load target resource as event.input for instance operations
- Ensure type-level operations invoked at instance URL use request body instead

Signed-off-by: Rahul Agarwal <rahul@medplum.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Signed-off-by: Rahul Agarwal <rahul@medplum.com>
Signed-off-by: Cody Ebberson <cody@ebberson.com>
Co-authored-by: Claude <noreply@anthropic.com>... (continued)

17302 of 19609 branches covered (88.23%)

Branch coverage included in aggregate %.

6 of 6 new or added lines in 1 file covered. (100.0%)

31415 of 33157 relevant lines covered (94.75%)

13708.74 hits per line