Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to MDHT 3.0 #118

Open
unixoid opened this issue Jul 18, 2016 · 7 comments
Open

Upgrade to MDHT 3.0 #118

unixoid opened this issue Jul 18, 2016 · 7 comments
Labels

Comments

@unixoid
Copy link
Member

unixoid commented Jul 18, 2016

The development of MDHT is being continued on http://projects.eclipse.org/projects/modeling.mdht. MDHT is even a Maven project now, but its JARs do not seem to be published. Therefore I cloned https://git.eclipse.org/r/mdht/org.eclipse.mdht (branch "mars"), build the JARs by myself, and made some changes to the IPF code -- see commit 9d307e0 in the IPF branch "mdht30".

Problems/doubts:

  • the unit test org.openehealth.ipf.modules.cda.CDAR2ValidatorTest#validateCCDError fails (set to Ignore for the time being).
  • org.openehealth.ipf.modules.cda.CDAR2Utils became somehow redundant because MDHT 3.0 contains only one CDAPackage.

Any hints will be highly appreciated. Please feel free to take over this upgrade -- I just have seen a presentation about the MDHT some days ago and wanted to look whether IPF can use this new version...

@ohr ohr added the change label Jul 18, 2016
@unixoid
Copy link
Member Author

unixoid commented Jul 18, 2016

BTW, the presentation I mentioned is available under https://wiki.phdsc.org/images/3/39/MDHT_on_FHIR_07-11-2016.pdf. MDHT 3.0 supports FHIR, but I am not sure that we need this...

@jkiddo
Copy link

jkiddo commented Sep 1, 2016

The diff between the test files that are used in the tests of CDAR2ValidatorTest (InvalidCCDDocument.xml and SampleCCDDocument.xml) is found on line 10 (the extension "POCD_HD000040_INVALID")and line 109 (serviceEvent classCode). I would expect the validator to find the extension on line 10 and throw an error on that. It is however not the current case

@jkiddo
Copy link

jkiddo commented Sep 1, 2016

Given that the typeId does not follow the standard, (as mentioned the typeId is bad - http://www.cdapro.com/know/25007) it is a bug that it validates. Now, the correct place to fix it would be in the mdht project, but who is in charge of that project?

@unixoid
Copy link
Member Author

unixoid commented Sep 1, 2016

The list of MDHT project members can be found on http://projects.eclipse.org/projects/modeling.mdht/who

@jkiddo
Copy link

jkiddo commented Sep 2, 2016

@jkiddo
Copy link

jkiddo commented Oct 24, 2016

Please be aware that using MDHT v3.0 causes a namespace change - eg. ClinicalDocument is in a package named org.eclipse.mdht.uml.cda.ClinicalDocument and NOT org.openhealthtools.mdht.uml.cda.ClinicalDocument

@unixoid
Copy link
Member Author

unixoid commented Mar 4, 2017

BTW, there seems to be another MDHT fork from Switzerland: sources, release JARs, snapshot JARS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants