I am developing an Android application to manage clinical data of Patient. I want to store the data in HL7 format in my device so that I can sync it with any third party system that supports openEHR HL7 framework... Any help on how I can achieve this.. Also any link or tool that I can use to create a PoC to demonstrate the HL7 format transactions ?
Hello @ppazos .
When I commit a composition to EHRServer, it can take up to a couple of minutes until that data shows up on any given query. The data is instantly available on the Web Console, however there is a latency until that same data can be accessed via query. Why is that? Is there any way (configuration, etc) to shorten or remove this latency at all?
I'm currently building an application and we're thinking this delay may cause some troubles. I'm using EHRServer v1.5 btw.
I think there is an option in Grails to trigger the job programmatically
@ppazos
Hello,
I have a problem with autorization - I have got a 401 code, instead of 200. The only solution is to generate a new API TOKEN from EHRServer (2.3) and replace it, but when I am trying to delete an old one I have an issue (login as an admin@cabolabs.com):
Error: access denied
Path: /organization/deleteApiKey/2
I don't want to generate a new api token every time :/
@kamil5325 BTW the permission thing is already fixed on master https://github.com/ppazos/cabolabs-ehrserver/commit/d0af5ce20c11724c9fd5e7f772a84d8250aaa842#diff-0c911c0854e763addc9ffce9e80f0325bfc30e9b0800cb29ee15d5eff0cad498R154
@kamil5325 I don't recall having an explicit expiration for tokens, you can check the token with a base64 decoder, the last part is the payload, and should have the expiration set if it expires https://github.com/ppazos/grails-security-stateless-ng/blob/master/src/main/groovy/net/kaleidos/grails/plugin/security/stateless/token/JwtStatelessTokenProvider.groovy#L49
Also, if you are running EHRServer in DEV mode, the database will be deleted each time you stop the application and regenerated each time you run it. You need to be sure you run in PROD to avoid losing keys. You can check the database between runs. Also check the guide https://cloudehrserver.com/learn
@ppazos I am in PROD, i don't lose keys. I checked with decoder and there is a 24h expiration.
This is an example from my EHRServer
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6Impkbmpwb3BneWd1ZmZmb3N4YnZkcmNkcmZmZm1lb29reXV1aGNtam1zbHV5eXNlbmhzQGFwaWtleS5jb20iLCJleHRyYWRhdGEiOnsib3JnYW5pemF0aW9uIjoiMTIzNDU2Iiwib3JnX3VpZCI6ImU5ZDEzMjk0LWJjZTctNDRlNy05NjM1LThlOTA2ZGEwYzkxNCJ9LCJpc3N1ZWRfYXQiOiIyMDIxLTAzLTIzVDE5OjIyOjEyLjQ1MVoiLCJleHBpcmVzX2F0IjoiMjAyMS0wMy0yNFQxOToyMjoxMi41NTlaIn0.UFyggsUyEtxnxxFr6FswkiKTHHyzVQu2NHqSwTWtuyE
This is an example from my EHRServer
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6Impkbmpwb3BneWd1ZmZmb3N4YnZkcmNkcmZmZm1lb29reXV1aGNtam1zbHV5eXNlbmhzQGFwaWtleS5jb20iLCJleHRyYWRhdGEiOnsib3JnYW5pemF0aW9uIjoiMTIzNDU2Iiwib3JnX3VpZCI6ImU5ZDEzMjk0LWJjZTctNDRlNy05NjM1LThlOTA2ZGEwYzkxNCJ9LCJpc3N1ZWRfYXQiOiIyMDIxLTAzLTIzVDE5OjIyOjEyLjQ1MVoiLCJleHBpcmVzX2F0IjoiMjAyMS0wMy0yNFQxOToyMjoxMi41NTlaIn0.UFyggsUyEtxnxxFr6FswkiKTHHyzVQu2NHqSwTWtuyE
@kamil5325 I found it, check the config stateless.expirationTime https://github.com/ppazos/cabolabs-ehrserver/blob/master/grails-app/conf/application.yml#L16
Hello @ppazos .
At my company, we've been using the EHRServer for some developments.
Now, we want to go into production, and for that, we want to install a new instance of the EHRServer on a new server. As it is a new install on a new server, we will have to upload the templates and queries on the new EHRServer. The templates upload seem to be straightforward. The queries though, not so much. Is there a simple way to "extract" the queries from our existing EHRServer to the new one? The alternative is to manually re-create all the queries, which can be error-prone and take some time.
Plus, are there any other details we have to take into account when using EHRServer in production instead of dev?
We're on v1.5.
Thanks.
At my company, we've been using the EHRServer for some developments.
Now, we want to go into production, and for that, we want to install a new instance of the EHRServer on a new server. As it is a new install on a new server, we will have to upload the templates and queries on the new EHRServer. The templates upload seem to be straightforward. The queries though, not so much. Is there a simple way to "extract" the queries from our existing EHRServer to the new one? The alternative is to manually re-create all the queries, which can be error-prone and take some time.
Plus, are there any other details we have to take into account when using EHRServer in production instead of dev?
We're on v1.5.
Thanks.
If you want to migrate data, you can try the sync API
Or you can do a mysqldump
In PROD I deploy the .war into a Tomcat server, certain versions of Tomcat work with certain versions of Java, I think I have Tomcat 8 and JDK 8 for EHRServer 1.5
Then configure the ENVVARS needed for prod, nothing special, take into account the folder/file access from Tomcat might change because the working folder is different, but those values can be set in the Config
Also would be nice to know more about your project so we can highlight it on Who is using EHRServer? docs, videos and blog posts
Hi @ppazos . Thank you for the suggestions.
Regarding the 'sync' option, from what I've read on the EHRServer guide, this is intended for high availability, load balancing, etc. That's not what we're looking for in this scenario.
With the 'mysqldump' solution, we would copy all data to our new PROD server. It's not what we intend either.
What we specifically want is to migrate the templates and queries from our dev EHRServer to a new one. We don't want the existing EHRs or contributions, as these were used only for development and tests, and now we want a new EHRServer that will only hold "real data" from real people. Therefore, we only want to use the templates and queries form our existing EHRServer.
Regarding the 'sync' option, from what I've read on the EHRServer guide, this is intended for high availability, load balancing, etc. That's not what we're looking for in this scenario.
With the 'mysqldump' solution, we would copy all data to our new PROD server. It's not what we intend either.
What we specifically want is to migrate the templates and queries from our dev EHRServer to a new one. We don't want the existing EHRs or contributions, as these were used only for development and tests, and now we want a new EHRServer that will only hold "real data" from real people. Therefore, we only want to use the templates and queries form our existing EHRServer.
As for sharing more more details on our project, sure, I think we could tell you a little bit about it. Maybe once it is up in production we could do that, as for now we're still in development and in a bit of a hurry.
With mysql dump you can actually export only the tables for AQL, and if you export everything, you can select which tables to import. https://dba.stackexchange.com/questions/9306/how-do-you-mysqldump-specific-tables
IMO both are valid solutions for your requirement.
To migrate templates you can just copy the files and reindex the OPTs.
What you mention also gives me the idea of constraining the objects that should be synced using the sync API, like having an extra option to select to sync "opts and queries" only. That might be a good feature for the future!
If you need help with the implementation, we provide consultancy for that, especially if you are in a hurry and you don't have time to figure out all the small details, I can help.
Thanks.
I think for now we will go with re-uploading the templates on the new instance and re-creating the queries manually. It's the solution we feel most confident about. The solutions you provided sound promising, but we don't want to "dive into new territory" at this stage. We'd rather stick to what we know, and we know that uploading the templates and creating the queries work and we know how to do it.
I think for now we will go with re-uploading the templates on the new instance and re-creating the queries manually. It's the solution we feel most confident about. The solutions you provided sound promising, but we don't want to "dive into new territory" at this stage. We'd rather stick to what we know, and we know that uploading the templates and creating the queries work and we know how to do it.
@ppazos primero que todo, muchas felicitaciones por su trabajo.... tengo una pregunta sencilla... espero que no se halla hecho antes ... si es así disculpen pero realmente no lo encontré.
Estoy corriendo el proyecto y todo va perfecto.... pero cierro el SSH del servidor y se baja el servicio.... como hago para dejar corriendo el EHRServer en la maquina?
Espero a ver sido claro!
En linux también se puede correr un proceso en segundo plano desde la terminal que no se cierre al cerrar la conexión, pero eso no te proporciona un servidor de producción, es solo Grails corriendo en PROD (Grails PROD no es para producción, sino que es para en desarrollo probar la aplicación como si estuviera corriendo en producción usando un Tomcat que tiene embebido Grails)
Si tienes dudas, todo eso está explicado en la documentación de Grails
hi @/all, do you know openEHR has a really nice forum here? https://discourse.openehr.org/ you can ask EHRServer and openEHR Toolkit questions there too, you just need to tag these conversations with the category "Tool Support", I take a look at that forum at least 3 times a week.
@/all we are working in the https://github.com/ppazos/openEHR-OPT adding some features that will be integrated into the EHRServer, like JSON schema validation, COMPOSITION validation using the Operational Template definition, bidirectional transformations between the openEHR canonical XML and JSON formats, and more. The openEHR-OPT can be used as a library in your projects or as a standalone CLI tool.
@/all The #openEHR Toolkit new version is ready! We are formally ending the BETA phase with a new look, better account management, improved tools, and the new "team accounts", see more at: https://toolkit.cabolabs.com/
Next week I'll release a document based on the #openEHR conformance work I've done for #HiGHmed and the exchange at had with openEHR SEC members. This document will help companies to prepare to the openEHR Conformance Verification, and later for openEHR Conformance Certification