Actors and Capabilities
This section describes the interoperability domains covered in this guide as well as the included actors and capabilities of each domain. Each domain includes an actors- and transactions diagram, a summary of the involved actors as welll as detailed descriptions of each transaction. In addition to text descriptions, each actor and their needed capabilities are also structured on the resources ActorDefinition and CapabilityStatement on referred subpages.
Medical record indexing
This section defines the actors and transactions covered in this implementation guide. The figure below shows the actors involved in medical record indexing and the relevant transactions between them.
Descriptions of actors
| Actor name | Description | Realization example |
|---|---|---|
| Medical Record Index | Registry for storing indices of medical records of patients spread out in different systems at different care providers. | PDI (patientdataindex) developed by the Swedish eHealth Agency |
| Medical Record Index Writer | System responsible for the registration and unregistration of medical record indices. | EHR system used by a care provider in Sweden. |
For further details on each actor and what capabilities they support, see sub pages Medical Record Index and Medical Record Index Writer.
Transactions
Create index record
When a new patient-care provider relationship has been created and health information is made available for exchange, the medical record index writer should send a request to create a new index record. The medical record index receives and manages this request.
This transaction is made possible through the Create Index Record operation. Please follow the link for more details.
Unregister index record
When a care provider stops making the health information available for exchange the medical record index writer requests to unregister the earlier created index record. The medical record index receives and manages this request.
This transaction is made possible through the Unregister Index Record operation. Please follow the link for more details.
Endpoint registry
This section defines the actors and transactions covered within Endpoint registry. The figure below shows the actors involved and the relevant transactions between them.
Descriptions of actors
| Actor name | Description | Realization example |
|---|---|---|
| Endpoint Registry | Registry for storing information about technical endpoints for retrieval of health information. | NTK (Nationell tjänsteadresseringskatalog) developed by the Swedish eHealth Agency. |
| Organization Endpoint Writer | System that provides information about technical endpoints to the endpoint registry. | System used by a EHR vendor or a care provider in order to automatically administrate endpoints in NTK. |
| Enpoint Consumer | System that consumes information about the technical endpoints stored in the registry. | System used by a EHR vendor or a care provider in order to automatically administrate endpoints in NTK. |
For further details on each actor and what capabilities they support, see sub pages Endpoint Registry, Organization Endpoint Writer and Endpoint Consumer.
Transactions
Add organization to endpoint
When a new organization has started to make health information available through an existing endpoint, the Organization endpoint writer can add this organization to the endpoint in the Endpoint registry.
This transaction is made possible through the AddOrganization operation. Please follow the link for more details.
Remove organization from endpoint
When an organization stops making health information available through an endpoint, the Organization endpoint writer can remove this organization from the endpoint in the Endpoint registry.
This transaction is made possible through the RemoveOrganization operation. Please follow the link for more details.
Search endpoints
Endpoints and related information can be retrived through searching, read more about it here here. Please follow the link for more details.
Medical record locating
This section defines the actors and transactions covered within Medical record locating. The figure below shows the actors involved and the relevant transactions between them.
Descriptions of actors
| Actor name | Description | Realization example |
|---|---|---|
| Medical Record Locator | System that supports locating medical records for a specific patient. | PDI (patientdataindex) developed by the Swedish eHealth Agency |
| Medical Record Location Consumer | System that is in need of consuming the location of medical records | Access service used by a patient or health care provider |
For further details on each actor and what capabilities they support, see sub pages Medical Record Location Consumer and Medical Record Locator.
Transactions
Locate records
In order to fetch health information about a patient, a medical record location consumer can request a list of endpoints and related organizations (care providers) from the medical record locator. The request requires specifying the patient as well as the API specification for the type of health information that is of interest.
This transaction is made possible through the Search Endpoint operation. Please follow the link for more details.