These pages describe the behavior 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 monitored and handled. Also described is the periodic importing of organizations.
...
When a user performs login at the eHealth Infrastructure, various checks are performed and security artifacts (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:
Zero, one or many different careteams in which the user can have one to or many user roles
Zero, one or many user roles in the organizational scope
...
The Clinical Administrator can define a PlanDefinition, its activities in referenced ActivityDefinition, possible Questionnaire to be answered, and add zero, one or more Library resources each containing a rule. The Library of interest here are those of automated processing type that are is attached to a plan for which a measurement has been successfully submitted.
...
Overall, the automated processing of a submitted measurement is asynchronous and constitute constitutes the following handling as a response to a submitted measurement event (which contains a reference to a Provenance resource referencing the measurement resources):
...
The automated processing of submitted measurement measurements is shown in the sequence diagram Automated Processing of Measurements.
...
A measurement has been submitted at an unexpected time when:
the scheduled timing is specified as
(Timing.repeat).dayOfWeekand the day of week code is not identical to that corresponding to the measurement submission time, orthe scheduled timing is specified with
(Timing.repeat).timeOfDayand(Timing.repeat).boundsDurationand the measurement submission time is not within the period (start and end included):start of period:
(Timing.repeat).timeOfDayend of period:
(Timing.repeat).boundsDurationadded to(Timing.repeat).timeOfDay
In case the ServiceRequest has ServiceRequest.Period or ServiceRequest.occurenceDateTime then it is not checked.
In case a measurement has been submitted at an unexpected time, automated processing produces:
...
When a measurement is submitted to the infrastructure, it triggers the automated processing of rules described in the following. Each submitted measurement is related to an activity in a citizen plan represented as a CarePlan where each activity is a ServiceRequest. Which rule or rules are involved depend depends on the PlanDefinition and its comprised ActivityDefinition resources referenced from the CarePlan and ServiceRequest resources, see https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/1661141027/Creating+Care+Plans#Applying-a-PlanDefinition-to-create-CarePlan(s).
An automated processing rule is a Library where Library.type is automated-processing. The existing Library are is listed in Library Resources. The automated processing rule Library eligible for a particular ServiceRequest are those zero, one, or more Library related to the ActivityDefinition referenced by the ServiceRequest.
...
The Library.parameter element specifies what resources are to be made available to the Library’s rule execution as input and what is returned as output. Typically, a measurement resource - be that an Observation, QuestionnaireResponse, or Media - is provided as input as part of the evaluate operation.
It is possible to state further input for both calculation-type Library (where Library.type is logic-library) and automated processing-type Library (where Library.type is automated-processing). For the calculation-type, all input resources must be provided as part of the evaluate operation.
...
For automated processing rules, there is a structure, AutomatedProcessingDTO, which lets the rule control aspects of the outcome of evaluating the rule. By adding to the structure, the rule controls if and in what number ClinicalImpression, Task, and Communication resources are created. A special case is the property activateSelfTreatment which controls whether a check on certain ServiceRequest resources should be made, possibly leading to an update of the status of eligible ServiceRequest resources (see further details in Activation of suspended Self-treatment type ServiceRequest ).
...
For each automated processing type Library evaluated, the returned GuidanceResponse typically contains a an AutomatedProcessingDTO with instructions for further processing.
...