Operation Definitions

For scope and usage of Operation Definitions please refer to the FHIR Documentation. The underlying business logic is not modelled in FHIR and has to be handled in external service classes. Please also refer to the HAPI Documentation.

For OMI we defined 3 operations that provide needed functionality for:

• creating a new entry in the OMI registry,
• update a entry already existing in the OMI registry and
• provide a heartbeat with up to date information about a service which is provided via the OMI platform.

Each of these operations is defined with in- and output parameters. The following table gives an overview on the definitions