We used Consol2 as our benchmark for changes during the change over to eclipse but perhaps this particular constraint was not in consol2
on another note - your issue talks about mdht being a maven project but having some issues which we are aware of -
the general issue developers run into is that we use tycho to support our dependencies which works very well -
the files are deployed to a p2 repository which when referenced from another tycho maven build pulls down all the dependencies
so in a tycho maven project we can use
<dependency>org.eclipse.cda.uml</depedency> and it will operate appropriately
the issue is most people use mdht dependencies in other tycho build - we had reached out to the tycho project to see if others have similar requirements but got no response
the appropriate path is allow a dependency such as above properly resolve dependencies - this will probably required a maven plugin which we have not had time/resource to implement
if you know if someone with maven plugin experience who would be willing to assist use that would be most appreciated
thanks
Sean Muir
MDHT
Long story short, I've been using the ipf project (
https://github.com/oehf/ipf) for doing some CDA validation tasks. ipf depends on MDHT but have been using an older version. Now, as seen on
https://github.com/oehf/ipf/issues/118, actions have been carried out to update the dependencies to a newer MDHT version, however, there seems to be some unit on the ipf side that no longer works as expected.
To be specific, it regards the validation of a Clinical Document.I would expect that a Call to CDAUtil.validate would inspect the typeId to see if it conforms to both the root and extension being
2.16.840.1.113883.1.3 and POCD_HD000040. This is however not the case. Is that intentional?
--
_______________________________________________
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