Best practice for updating templates

What do you mean by

load the template on startup

When the server is started for the very first time?

1 Like

Yes, exactly, and on restart too (although in that case you’d expect it to detect that it’s already loaded).

I guess it’s similar to the way HAPI FHIR can load implementation guides on startup, I wondered if EHRBase could do a similar thing for templates.

1 Like

Interesting idea - might even be possible to use FHIR IGs for that purpose.

FWIW - we use a Postman script for this kind of standard loading of templates plus associated sample compositions.

2 Likes

Inside the openEHR SDK, there is an interface for a TemplateProvider. The default client (openEHR_SDK/client/src/main/java/org/ehrbase/openehr/sdk/client/openehrclient/defaultrestclient/DefaultRestTemplateEndpoint.java at develop · ehrbase/openEHR_SDK · GitHub) implementation of this TemplateProvider checks a folder and synchronizes the EHRbase server. We use this mechanism in the integration components like FHIR Bridge (and our commercial CDR Bridge) to ensure all templates are in place.

So you could quite easily incorporate a mechanism like this as part of a batch file for system startup or your CI/CD pipeline.

4 Likes