...
Minimize the amount of data that the backend-for-frontend (BFF) has to calculate on
If the vendor a telemedicine solution or application requires a BFF try to minimize the amount of data that the backend-for-frontend (BFF) has to calculate on
...
Target user interface design to microservices (see above Design Guide)
Avoid prefetch of data for e.g. details view in a master-detail pattern
Prefer calling eHealth services directly, only use BFF pattern if really needed
Only do caching in vendor application telemedicine solutions or applications if really needed
…
Avoid pre-fetching of data
...
Caching are both provided by the eHealth Infrastructure that performs server-side caching, but can also be done in Vendor Applicationssolutions or applications.
See https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/1034354702/Technical+Interactions+with+Services#Caching-on-Searching on caching provided by the infrastructure.
See Client-side caching for recommendations on caching in the Vendor telemedicine solutions and applications.
Take advantage of the eHealth Infrastructure Event Model
Infrastructure events can be used in Vendor Applications telemedicine solutions or applications to trigger functionality.
...
patient created,
patient updated,
Careplan careplan created,
…
Vendor applications Applications should subscribe to events, instead of polling for changes. Using events is considered more effective than polling for changes.
The events can be used in Vendor Applications applications to e.g. update cached information
...
Provide as parameter in querying the FHIR services to limit the results, the eHealth services will then filter and limit the results returned to the client.
E.g., only episode of care relevant to selected care-team
E.g., only tasks relevant to selected care-team
Reduce response times from eHealth services
Minimize data and thereby work in Vendor Applicationstelemedicine solutions or applications.
Reduce the risk of UTH (adverse events, Danish: utilsigtet hændelse)
...