Behind the Scenes
- Erik Nielsen
- John Schneider
- Ole Loft (Unlicensed)
This page and subpages describe the 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 is monitored and handled. Also described is the periodic importing of organizations.
Sub-pages
- Automated Processing — The eHealth system runs automatic processes that happen either on a schedule or when triggered by specific events. This page explains these automatic processes.
- Importing and updating Organization information from SOR and FK-Organisation into eHealth Infrastructure — The eHealth Infrastructure performs the import of organizations' information from Sundhedsvæsnets Organisationsregister (SOR) and KOMBIT Fælleskommunalt (FK) Organisation (formerly Støttesystemet Organisation (STS-ORG)) to the eHealth Infrastructure daily.
- Video endpoint federation (VDX)
- Generation and Control of Infrastructure Communication (Messages and NemSMS) — The messages are represented by FHIR Communication resources and can be created either by the infrastructure itself—often as part of automated processing workflows—or by User Systems, depending on the context of the interaction or the operational requirements.
- NemSMS from SSL application — Description of what happens behind the scenes in the SSL application in “opret kommunikation”
- Sharing through Registering Documents in National Document Sharing Infrastructure
- Synchronization of National patient data
Content
Handling at Login
When a user performs login at the eHealth Infrastructure, various checks are performed and security 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:
Zero, one or many different careteams in which the user can have one or many user roles
Zero, one or many user roles in the organizational scope
For the recognized user roles bound to a recognized and pre-existing CareTeam, it is ensured that:
a
CareTeam.participantexists where theCareTeam.participant.memberreferences the Practitioner. A participant can have multiple roles in a CareTeam.If such an entry is not present or does not contain the current role then the CareTeam is updated.
When a
CareTeam.participantis added, theCareTeam.participant.periodis set with aPeriod.startof date/time at update. ThePeriod.endis left without value to form an open-ended period.
For all the organizational scopes where the organization identification can be resolved to an Organization in the eHealth Infrastructure, it is ensured that:
a PractitionerRole exists where the
PractitionerRole.practitionerreferences the Practitioner and thePractitionerRole.organizationreferences the Organization