Hi all,
I’m playing with the TD v2.7.60Beta to include openEHR template support to CaboLabs EHRServer (http://www.youtube.com/watch?v=D-hs-Ofb8SY)
I opened the Blood Pressure archetype and tryied to constraint the Any Event node of type EVENT to allow only POINT_EVENT, and I get this rule:
**PointInTime**Shouldn’t “PointInTime” be “POINT_EVENT”?
Is there any reason for the TD to not use openEHR datatype names?
Where can I find all the names used to constraint allowedTypes in TD?
Thanks!
Hi Pablo,
The OET format is an internal format. You should export the template as an OPT and you will get a AOM and RM based output.
Heath
Hi Heath,
I have a related question about OPT.
Could you explain path calculation algorithm for OPT?
Best wishes,
Shinji KOBAYASHI
Hi Shinji,
Can you be more specific about your question?
Heath
Hi Heath,
I am trying to implement opt_parser on Ruby.
Parsing OPT XML file is easy, but the path of each node is not defined.
There are many path example around archetypes, but template path has
only few example.
Moreover, OPT has nested archetype tree. I am confused much.
Best wish,
Shinji
Hi Shinji,
Look at the SemanticHealthNet Heart Failure Summary template at
http://openehr.org/ckm/#showTemplate_1013.26.14_2, and press the "Show
Pathjs" button , you will see all of the paths within the template.
Also you might find it helpful to look open a complex template in
Template Designer and look at the Path property in the Properties box.
Ian
Hi Pablo,
I just want to re-emphasise Heath's point for anyone looking to
implement openEHR template support. Your start point should be the
.opt 'Operational template' format. This is what is used by a number
of developers to generate downstream artefacts such asd code
fragments, xsd schema and GUI generation.
The official openEHR templates will be fully based on ADL1.5, rather
than the current mix of ADL1.4 and Ocean .oet, but the eventual ADL
1.5 .opt output will be very similar to the current .opt, so this is a
good 'junction point' for transition from ADL1.4 -> ADL 1.5
Ian
Thank you Ian. This is quite informative.
Regards,
Shinji
Hi folks,
We used opt to feed in the model to software, especially the GUI generator in GastrOS.
We added a few GUI Directives to get the desired looks...
I reckon the new version of TD now supports those directives 
For those interested it is open source at: http://gastros.codeplex.com
Cheers,
-koray
Hi Ian & Heath, thanks for the input. I was studying the different formats and the TD, now I get it 
Work is ongoing to support OPTs on EHRServer, as the source of data definition to index data for querying.
I’ll wait a little to implement ADL 1.5 since I invested a lot of time on getting my infostructure to work with ADL 1.4.
Maybe someone from the community wants to help on that part. Partners are always welcome!
Hi Shinji, I’ve created a script to traverse an OPT and generate paths like this:
/content[archetype_id=openEHR-EHR-SECTION.referral_details.v1]/items[archetype_id=openEHR-EHR-INSTRUCTION.request-referral.v1]/protocol[at0008]/items[archetype_id=openEHR-EHR-CLUSTER.individual_professional.v1]/items[archetype_id=openEHR-EHR-CLUSTER.person_name.v1]/items[at0013]/items[at0002]/items[at0003]/value DV_TEXT
This path was generated from the “Demo hide-on-form” OPT that is in the CKM. Don’t know if the syntax is 100% valid, but changing the algorithm is easy.
Algorithm: https://github.com/ppazos/cabolabs-ehrserver/blob/master/src/groovy/com/cabolabs/archetype/OperationalTemplateIndexer.groovy
Test: https://github.com/ppazos/cabolabs-ehrserver/tree/master/test
OPTs: https://github.com/ppazos/cabolabs-ehrserver/tree/master/opts
Thank you pablo.
These are encouraging.
Cheers,
Shinji