Difference between revisions of "Model Interchange Format"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 3: | Line 3: | ||
The MIF makes use of schema constructs including simple type patterns, the use of choice and sequence structures as well as cardinality and attribute use to reflect HL7 requirements as tightly as possible. In some cases, w3c schema is not capable of expressing the rules required by HL7. In these cases, the rules are either encoded as embedded Schematron rules or by listing them as “programmatic” rules at the beginning of the schema. Instances must comply with the Schema, Schematron and programmatic rules to be considered HL7-compliant instances. | The MIF makes use of schema constructs including simple type patterns, the use of choice and sequence structures as well as cardinality and attribute use to reflect HL7 requirements as tightly as possible. In some cases, w3c schema is not capable of expressing the rules required by HL7. In these cases, the rules are either encoded as embedded Schematron rules or by listing them as “programmatic” rules at the beginning of the schema. Instances must comply with the Schema, Schematron and programmatic rules to be considered HL7-compliant instances. | ||
| − | + | The definition of the MIF is a task of the [[Tooling Work Group]]. The MIF files are contained in the v3 publications. Comments can be submitted to the [mailto:tooling@lists.hl7.org HL7 Tooling list] or [mailto:lloyd@lmckenzie.com Lloyd McKenzie]. | |
==External links== | ==External links== | ||
*See [http://www.ringholm.de/docs/03060_en_HL7_MIF.htm MIF Whitepaper] (with embedded Video explanation of the MIF). | *See [http://www.ringholm.de/docs/03060_en_HL7_MIF.htm MIF Whitepaper] (with embedded Video explanation of the MIF). | ||
*See [http://www.umlbof.org/wiki/index.php?title=MIF_Mapping_Issues MIF to UML mapping issues] | *See [http://www.umlbof.org/wiki/index.php?title=MIF_Mapping_Issues MIF to UML mapping issues] | ||
| + | *The released coremifs and (annotated) schema's can be found at [http://gforge.hl7.org/gf/project/design-repos/frs/?action=FrsReleaseBrowse&frs_package_id=103] and at [http://gforge.hl7.org/gf/project/mif-schemas/frs/?action=FrsReleaseBrowse&frs_package_id=14]. | ||
Revision as of 10:48, 28 October 2009
Glossary definition: The Model Interchange Format (MIF) is a set of XML formats used to support the storage and exchange of HL7 version 3 artefacts as part of the HL7 Development Framework (HDF). It is the pre-publication format of HL7 v3 artefacts used by tooling. The formats are defined by a set inter-related schemas. The MIF serves to document the HL7 metamodel, identifying all data elements of interest to version 3, as well as indicating correspondance to the UML meta-model.
The MIF makes use of schema constructs including simple type patterns, the use of choice and sequence structures as well as cardinality and attribute use to reflect HL7 requirements as tightly as possible. In some cases, w3c schema is not capable of expressing the rules required by HL7. In these cases, the rules are either encoded as embedded Schematron rules or by listing them as “programmatic” rules at the beginning of the schema. Instances must comply with the Schema, Schematron and programmatic rules to be considered HL7-compliant instances.
The definition of the MIF is a task of the Tooling Work Group. The MIF files are contained in the v3 publications. Comments can be submitted to the HL7 Tooling list or Lloyd McKenzie.
External links
- See MIF Whitepaper (with embedded Video explanation of the MIF).
- See MIF to UML mapping issues
- The released coremifs and (annotated) schema's can be found at [1] and at [2].
