Re: [xml-dev] XML Schema as a data modeling tool

The current version is 2.4.2 available from Launchpad as you noted. All published versions as well as the upcoming 2.4.3 are available from GitHub https://github.com/mlhim/specs

The history is that we began in 2009 with 1.x to be compatible with openEHR. However, the more we worked on it the more we realized what was unnecessary so we removed it.

There is a site Healthcare Knowledge Component Repository http://hkcr.net/ that has example CCDs from various reference model versions. Though this site hasn't been kept up to date since we published the CCD-Gen (CCD Generator) and the various academic projects have gotten underway. At one point we had all of ICD-10 modeled on the site. Since they were on RM 2.4.0 we removed them. We are currently modelling all of the NCI Common Data Elements (CDEs) and CRFs. The CCD-Gen allows us to create reusable complexTypes (we call Pluggable Complex Types or PCTs) for the CDE models and full CCDs as the CRFs. See: https://wiki.nci.nih.gov/display/caDSR/CDE+Browser

On Wed, Oct 2, 2013 at 10:16 AM, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:

Timothy,

cordial thanks, this looks exciting, and I will study the approach taken by the MLHIM thoroughly.

For now just one question: is the current reference schema fully contained in mlhim2.xsd, downloadable from https://launchpad.net/mlhim-specs ?

Thank you,
kind regards,

Hans-Juergen

Von: Timothy W. Cook <tim@mlhim.org>
An: Hans-Juergen Rennau <hrennau@yahoo.de>
CC: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Gesendet: 14:06 Mittwoch, 2.Oktober 2013
Betreff: Re: [xml-dev] XML Schema as a data modeling tool

Hi Hans-Juergen,

This is exactly what we do with Multi-Level Healthcare Information Modelling (MLHIM).

We have a generic reference model in XML Schema 1.1 and then develop concept models as constraints against the reference model. The concept models are called Concept Constraint Definitions (CCDs). Since each reference model can exist forever, each CCD also offers the permanence required for longitudinal healthcare applications. Since the models offer syntactic and semantic constraints outside of the application code and database structure, they can be shared for interoperability.

You can find out more from:

http://www.mlhim.org

https://github.com/organizations/mlhim

and on YouTube see the two playlists:
Healthcare Modeling Q&A and Healthcare IT Live!
https://www.youtube.com/user/MLHIMdotORG

We are also on Google+ at:
http://gplus.to/MLHIM and http://gplus.to/HealthcareIT

Though the reference model does have a small amount of healthcare semantics (in the Entry children) it can be easily used in any industry.

Any questions, please feel free to ask.

We do have a (not open source) tool to generate CCDs. There is an open source tool on GitHub, that is partially finished just waiting on developers.

--
MLHIM VIP Signup: http://goo.gl/22B0U
============================================
Timothy Cook, MSc +55 21 94711995
MLHIM http://www.mlhim.org
Like Us on FB: https://www.facebook.com/mlhim2
Circle us on G+: http://goo.gl/44EV5
Google Scholar: http://goo.gl/MMZ1o
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook