Performance Considerations

The eHealth Infrastructure consists of a large set of APIs that are designed to support common workflows in applications for the telemedicine domain.

To ensure proper use of the shared resources, it is important to consider the performance of the client applications and the way they access data in the Infrastructure.

This improves the end-user experience as well as the utilization of the common hardware resources.

Below, a list of best practices and anti-patterns a given to mitigate common issues i application design.

1. Don’t request Patient Context tokens pr. row in a list.
   The Patient Context is for focusing on a specific Patient. It ensures that all clinical information retrieved from is related to that Patient only. This helps the client app not to mix data from multiple Patients.
   For cross patient related lists such as:

   1. Task lists

   2. EpisodeOfCare list, showing a list of EoCs that a CareTeam is responsible for

   3. CarePlan list, showing a list of CarePlans that a CareTeam is responsible for

   4. A list of Communication resources, for showing an “inbox” for a CareTeam or a Practitioner

I might be necessary to display related Patient demographic information along with the Task (who is the subject of the Task), the EpisodeOfCare (who is the subject of the EoC) or the Communication (who is the Communication regarding).
For this the Patient demographic search using multiple Ids is designed to retrieve all the related Patient information in a single API call.