Please enable JavaScript.
Coggle requires JavaScript to display documents.
FHIR Metadata Service (Operation Definition (upload/import SAP delivered…
FHIR Metadata Service
- upload/import SAP delivered “OperationDefinition”,
so that it can be used in defining operations and query for the FHIR serve
- restrict modification to SAP delivered “OperationDefinition”,
so that it cannot be changed by Partners and core operations defined by SAP cannot be altered.
- upload/import “OperationDefinition”,
so that I can enhance/restrict the operations supported by the FHIR server
- validate “OperationDefinition”,
so that it can I can check if “OperationDefinition” is valid or no
- define input and output parameters for “OperationDefinition”,
so that I can also validate the request and response for the operation
- view the list of operations supported along with description and documentation for both operation and input/output parameters,
so that I can see all supported operations at one place
- implement the business logic for the defined operation so that I can handle request and response for that operation
-
-
- use defined “StructureDefinition” in a profile
- define “StructureDefinition” with either differential or snapshot or both,
so that I can consume both approaches based on the need.
- IWT use defined “StructureDefinition”
so that I can define new extensions for a profile
- trigger events during creation/modification for “StructureDefinition” for downstream processing like handling persistency and operations et
- define extensions using “StructureDefinition” using both simple and complex types,
so that I can modify the base resource
- validate profile,
so that I can check if changes are valid or not
- reuse the defined extension (StructureDefinition),
so that I can consume it in multiple profiles as required
- publish the profiles,
so that I can use it during operation invocation, validation, search etc
- view the list profiles,
so that I can re-use it further in profile
- trigger an event whenever profile is imported,
so that a business logic can be performed by the subscriber of the event
- define and maintain “CapabilityStatement”,
so that I can define the FHIR server functionality
- validate “CapabilityStatement”,
so that I can check if “CapabilityStatement” is valid or not.
- generate “CapabilityStatement” using the other conformance resources,
so that I do not have to create it from scratch.
- define “MessageDefinition”,
so that I can define messages relevant for integration scenarios like CIS, Payer, S4.
- implement “$version” operation,
so that it is possible for PaaS tenant to choose the right version
-
- define and maintain “SearchParameter”,
so that I can define search and filter criteria for a resource and its attributes
- validate “SearchParameter”,
so that I can check if “SearchParameter” is valid or not
- enable search on extension with “SearchParameter”,
so that I can also search on the extension attributes.
-
-