Hi all, I've created another client for EHRServer, now in PHP: https://github.com/ppazos/EHRClientPHP This new client is only for querying the EHR. The previous client, also does commits and is developed in Grails/Groovy/Java: https://github.com/ppazos/cabolabs-emrapp
Next thursday I'll be doing a small online demo in Hangout (it will be in spanish this time) -- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com From: [email protected] To: openehr-implementers at lists.openehr.org Subject: RE: Want to test an openEHR repository? Date: Mon, 9 Sep 2013 03:21:03 -0300 Hi all, I'll leave my machine on with the server running for anyone wanting to try things out, and maybe break something so I can fix it later :) Now introducing... http://ppazos.zapto.org:8090/ehr/ tada! I have committed a couple of compositions to EHR 1 (uid=3c7025cf-cf6f-4c3f-b0cc-1176475f0781) like the ones here: https://github.com/ppazos/cabolabs-emrapp/tree/master/committed And created a couple of queries, one to chart data and the other to get compositions: you must select an EHR in order to get data http://ppazos.zapto.org:8090/ehr/query/execute?uid=297c8014-7861-4a65-8652-ac1b4ec268cdhttp://ppazos.zapto.org:8090/ehr/query/execute?uid=be9466b1-fa90-400b-b454-67f94881a558 Of course, you can use the services specified here:https://github.com/ppazos/cabolabs-ehrserver Please send me al your comments about the system, the ui, the service API, errors you get, anything!The idea is to improve this and have an open source repo in the community to be used by all. Of course if you find bugs, please add an issue here: https://github.com/ppazos/cabolabs-ehrserver/issues -- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com Date: Mon, 9 Sep 2013 08:06:22 +0200 From: [email protected] To: openehr-implementers at lists.openehr.org Subject: Re: Want to test an openEHR repository? On 09/09/2013 05:58 AM, pablo pazos wrote: Hi Bert, For these points: "- In there is the element:<data xsi:type='COMPOSITION' archetype_node_id='openEHR-EHR-COMPOSITION.signos.v1'>I think this is a mistake. I think the attribute should be called different, f.e. archetype_id. - But this element should also have an archetype_node_id to store the archetypeNodeId of the definition, mostly containing at0000. - Also, I miss an archetype_id/value element in the XML, which should also store the archetypeId if there is one, which is in the composition." I reviewed the specs, this point is clear: see common.pdf, section 3.1.2 "Most classes in the openEHR reference model inherit from the LOCATABLE class, which defines the idea of ?locatability in an archetyped structure?. LOCATABLE defines a runtime name and an archetype_node_id. The archetype_node_id is the standardised semantic code for a node and comes from the corresponding node in the archetype used to create the data. The only exception is at archetype root points in data, where archetype_node_id carries the archetype identifier in string form rather than an interior node id from an archetype." Is that so? This really surprises me. There are so many arguments against that. - It leaves no room for an archetypeNodeId for the root. - One would wonder why it is there anyway if it cannot be stored, and the explanation in the ontology-section of an archetype gets lost also. - The archetypeId is also used in another syntactical way in paths (f.e. AQL) then the archetypeNodeId is. - And also, there is another room to leave the archetypeId, in the archetype_details-property. To handle the both different attributes in the same way under the same attribute-name seems not necessary, not logical, and confusing. I don't know if I will rewrite my software to do this. I must really think this over. But thanks, Pablo, for being so precise on this. Bert _______________________________________________ openEHR-implementers mailing list openEHR-implementers at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org _______________________________________________ openEHR-implementers mailing list openEHR-implementers at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130916/62a127ac/attachment.html>
