These are the specific business or transaction information objects that need to be instantiated to represent the context and substance needed to execute a given IIP transaction. The lifespan of these objects will start and end with the execution of each IIP being processed. The type of objects represented depends on the nature of the IIP being processed.
These services are responsible for processing business messages sent by a point of service applications to store or retrieve data in EHRi repositories or registries.
General Info | |
---|---|
Name | Domain Business Components |
Visibility | public |
Active | false |
Abstract | false |
Leaf | false |
Root | false |
Owner | Classes |
Operations | |
---|---|
Name | Return Type |
![]() | |
![]() |
Relations | |||
---|---|---|---|
Name | Type | Begins | Ends |
![]() | generalization | Domain Business Components | Business Services |
This service is initiated by the Longitudinal Record Services to manage the message interactions to record patient information in an EHRi repository or registry.
In the case where the system that manages the information to be recorded in the target repository / registry is external to the EHRi environment, this service will use and manage HL7 message interactions between the EHRi Transaction Processor and the external system to complete the process.
Note: It is expected that clinical information for EHRi Domain repositories such as Lab, Drug and DI etc, will be created directly by the PoS systems in the appropriate jurisdictional domains (e.g. Pharmacy systems, Lab Information systems, Radiology systems) and not by this service (See EHRS Blueprint v2.0 Section 4.3.7.3 Transaction Handling and LRS Operators)
General Info | |
---|---|
Name | Put EHRi Data |
Owner | Domain Business Components |
Concurrency | sequential |
Query | false |
Visibility | public |
Scope | instance |
Abstract | false |
Leaf | false |
Root | false |
This service is initiated by the Longitudinal Record Services to manage the interactions that query patient information from an EHRi repository or registry.
This service will use message header information to determine the target repository / registry location of where to retrieve the EHRi data.
Example patient centric repositories and registries this service will query are:
In the case where the system that manages the information to be retrieved from the target repository / registry is external to the EHRi environment, this service will use and manage HL7 message interactions between the EHRi Transaction Processor and the external system to complete the process.
General Info | |
---|---|
Name | Query EHRi Data |
Owner | Domain Business Components |
Concurrency | sequential |
Query | false |
Visibility | public |
Scope | instance |
Abstract | false |
Leaf | false |
Root | false |