Open Source Document Management System | OpenKM

We are looking for configuration suggestions to integrate this application with an EMR (Electronic Medical Records) application. While we can use API and maintain links in EMR system, we would also like to configure this application so that every document can be associated with following attributes:
1. Practice Identifier
2. Patient Record Number
3. Patient Name
4. Patient Date of Birth

Ideally these would be validated / fetched from the EMR API.

Thank you in advance for your suggestions.

We suggest:
1- One of the SDK's ( java. .net or php ) http://wiki.openkm.com/index.php/Third- ... n_problems otherwise you should create your own client for consume OpenKM REST API.
Some urls:
https://docs.openkm.com/kcenter/view/sd ... teDocument
https://docs.openkm.com/kcenter/view/sd ... tiesSimple
https://docs.openkm.com/kcenter/view/sd ... mples.html

2- You have two strategies, set some logic outside and when creating a document, first you create destination folder /okm:root/patients/number etc.... or create all documents always in the same place /okm:root/pending and then based on automation events, create your own catalog class for delegating the cataloging task to OpenKM ( http://wiki.openkm.com/index.php/Automation )

Thank you. Automation option will work very well for this since going through a tree of 10s of thousands of patient name/number will be impractical.

We are thinking of adding EMR data as keywords. So each document added through EMR will have key words as (for example) : 91504, John, Doe, 08/08/1980, 8979 where 91504 - Practice number, John Doe - Patient Name, 8979 - Medical Record Number.

We would appreciate suggestions for better alternatives for users without EMR access (using OpenKM native user interface directly).

Better than keyword create unique folder identifier like "00091504 - John Carpenter" or "000091504"

For cataloging you can use the folder name as /okm:root/0/0/0/9/00091504 ( depending the number of patients should be interested or more or less folders deep. For optimal performance we suggest 100-200 nodes per parent ( 200 children folders ).

In professional edition we had introduced records, in community you can use folders ( based on name unique ID ) what will going in similar way.

I am not sure if what i am going to tell will be helpful. But i think i know some of the systems that provide complete integration. One of the EHR systems that provide the capability is blueEHR. But it is a paid one, that charges based on subscription. And if you want to use a opensource one, go for OpenEMR or OpenMRS.








EHR systems