Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdht-dev] Modeling approach for pharm namespace
Supporting extensions is currently problematic within MDHT for CDA but i do have an approach - 

We looked into several ways including looking to leverage osgi fragments - the dependencies were difficult to define
(if you have a extension within datatypes - you can not specifically depend on a fragment)

The approach going forward is to split the current CDA plugin (which has more then just EMF code) into to several plugins

A emf code only - (base cda) - no extensions
A US realm extension
Nehta extensions
and the IHE extensions you are talking about


so to support extensions - you would clone the base cda project, add your extensions, regenerate the cda projects (cda,datatypes,…)

This is not optimal but is workable - we have not taken this step but need to soon so open to other options

(One of the other approaches considered was dynamic emf - but you do not have methods for the extensions but could potentially generate a extension interface and implementation which manipulates the base cda)

thanks

Sean
  





On Feb 1, 2016, at 6:15 PM, Oliver Egger <oliver.egger@xxxxxxxx> wrote:

Hello

As promised a new MDHT modeling question ... I could model all "regular" classes, constraints, however I am now stuck with modeling the pharm schema extension (http://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_PRE.pdf).

As an example they extended the cda:Material with a pharm:formCode between the name and the lotNumber

so instead of cda::Material which has
realmCode
typeId
templateId
code
name
lotNumberText

I need a PharmMaterial that has
realmCode
typeId
templateId
code
name
pharm:formCode
lotNumberText

For a first try i created the PharmMaterial in my ihe.pharm Model and extended (generalized) the PharmMaterial from rim::Entity, copied the elements from cda::Material and added a new formCode element. However there are warning during the build process:

 [cdatools] Cannot find CDA property for: pharm::PharmMaterialEntry::realmCode 

....

and the class which is generated has no access functions (realmCode, typeId ...) like  org.openhealthtools.mdht.uml.cda.Material has

So my questions:


  1. Is it possible to derive for a class from a RIM::Entity a have the code generation available in a own model?
  2. If no, would I have to modify the org.openhealthtools.mdht.uml.cda model? If I add a class there, how can I start the code generation?
  3. Is there another/simpler way to add elements to existing the CDA classes?
If you need further information do not hesitate to contact me, otherwise I'm looking forward for some hints ...

Thanks a lot in advance
Oliver






--
oliver egger


-->  30.3.2016: FHIR workshop und hands-on, www.ahdis.ch/anmeldung

mobile: +41765795005
twitter: @oliveregger

ahdis gmbh
agile health data information systems
bertastrasse 4
8003 zürich
switzerland
_______________________________________________
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev

Back to the top