-
Notifications
You must be signed in to change notification settings - Fork 5
API endpoints
EhrIds need to be existent in the openEHR platform.
List of ehrIds that you want to be linked or blank for converting every EHR contained in the platform.
If called, generates a link between person and EHR.
Depending on the application.yml setting, this can be either boilerplate persons for each EHR.
Otherwise, it will map the compositions that are defined in resources/person_data.
Before use the ehr needs to be linked using /person.
List of ehrs which compositions are to be tranformed, or blank to convert all the compositions of the ehrs that where linked using the person endpoint.
Automatically loads composition of ehrIds and transforms them into OMOP.
Requires compositions to be contained in order to generate output.
Triggers manually the generation of eras and periods, otherwise can be set using a cronjob in application.yml
Triggers Eos so that it generates the eras and periods tables in the OMOP CDM db.
Requires the ehrIds to be linked beforehead via /person.
Composition attached as json or xml.
Transforms composition into OMOP CDM.