Define FHIR custom operations

[joeflack4]

Description

Shahim brought this up at today's terminology meeting, and it sounded like a good idea to me.

To my understanding, this would be beneficial for us because:

• This could be a good way of defining our endpoints that are not FHIR-specific in a way that FHIR can understand.
• And it's also a good way to define specifications so that implementation is easier / more stable.

Related resources

https://www.hl7.org/fhir/operations.html https://www.hl7.org/fhir/operationdefinition.html https://www.hl7.org/fhir/implementationguide-definitions.html https://www.hl7.org/fhir/profiling.html#api

[joeflack4]

@ShahimEssaid I don't know much about this, but it sounded like a good idea to me. Just want you to be aware that this issue exists, and if you have anything to add, please feel free.

[ShahimEssaid]

FHIR operations are basically RPCs that go beyond what the FHIR REST methods can do: https://www.hl7.org/fhir/http.html