Excerpt |
---|
This page and subpages describe the behavior behaviour of services in the infrastructure which are not directly invoked by a client. What is described here is what happens when a user performs login, how submitted measurements are processed in automated processing, and how citizens' adherence to care plans are is monitored and handled. Also described is the periodic importing of organizations. |
...
Table of Content Zone | ||||||
---|---|---|---|---|---|---|
| ||||||
Handling at LoginWhen a user performs login at the eHealth Infrastructure, various checks are performed and security artifacts artefacts (such as the security token) are produced. In addition, certain resources are read, created, or possibly updated. The following applies to users of the Practitioner type. The external security token contains one to many organizational scopes in which the user can have:
For the recognized user roles bound to a recognized and pre-existing CareTeam, it is ensured that:
For all the organizational scopes where the organization identification can be resolved to an Organization in the eHealth Infrastructure, it is ensured that:
Sharing through Registering Documents in National Document Sharing InfrastructureSome FHIR resources in the eHealth Infrastructure are assembled to volatile FHIR Compositions (as described in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/2242281473/Performing+Document+Query+and+Retrieve+and+Using+Transformations#Preparing-Transformations-by-Assembling-Required-FHIR-Resources), transformed to Danish profiles of Clinical Document Architecture (CDA) documents (as described in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/2242281473/Performing+Document+Query+and+Retrieve+and+Using+Transformations#Transformation-Details), and registered in the national health document sharing archives. This way, the patient and other healthcare professionals can access the health data registered through other health systems while subjected to various access controls and audit logging. This description focuses on the criteria for this registration to take place. Document Registering of Measurement DataPrerequisites for Document Sharing of Measurement Data
Submitted measurements, whether in the form of Observation, QuestionnaireResponse, or Media, are each associated with a ServiceRequest. As part of being evaluated by a Practitioner, each measurement can be approved for sharing in the form of a ClinicalImpression with the element The criteria for registering a measurement as a document are:
An Observation is registered as a Danish profile of the CDA Personal Health Monitoring Report (PHMR) document and a QuestionnaireResponse as a Danish profile of the CDA Questionnaire Response Document (QRD) document.
Submitted measurements, whether in the form of Observation, QuestionnaireResponse, or Media, are each associated with a ServiceRequest. As part of being evaluated by a Practitioner, each measurement can be approved for sharing in the form of a ClinicalImpression with the element The criteria for registering a measurement as a document are:
It is also possible to allow the infrastructure to automatically approve the sharing of measurements, this is done by setting the An Observation is registered as a Danish profile of the CDA Personal Health Monitoring Report (PHMR) document and a QuestionnaireResponse as a Danish profile of the CDA Questionnaire Response Document (QRD) document. Document Registering of AppointmentsA created or updated Appointment (whether of profile ehealth-appointment or ehealth-videoappointment) is registered as the Danish profile of the CDA Appointment Document (APD), provided that criteria are met. The criteria for registering an Appointment resource are:
|