This wiki has undergone a migration to Confluence found Here
Difference between revisions of "VML Processing Widget"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
*consumes proposals for change expressed in the HL7 <big>'''[[Vocabulary Maintenance Language]] (VML)'''</big>, | *consumes proposals for change expressed in the HL7 <big>'''[[Vocabulary Maintenance Language]] (VML)'''</big>, | ||
*: | *: | ||
| − | * | + | *splits these proposals into two source streams targeted at the Access repository in which the HL7 Vocabulary content is stored:: |
| − | ** an SQL update stream and | + | ** an SQL update stream for updating files of properties assigned to vocabulary objects, and |
**: | **: | ||
| − | **an | + | **an XML sream processed in Java to update the primary Access tables |
**: | **: | ||
| − | *update the vocabulary content stored in | + | *:together, these streams update the vocabulary content stored in the Access repository, |
*: | *: | ||
| − | *" | + | *uses a Java process to "clean up" the Access content, |
*: | *: | ||
| − | *invokes RoseTree to express the vocabulary in HL7 Model Interchange Format (MIF), and | + | *invokes RoseTree to express the complete vocabulary content in HL7 Model Interchange Format (MIF), and |
*: | *: | ||
| − | *combines this with an externally maintained MiF extension file | + | *combines this MIF content from the Access repository with an externally maintained MiF extension file to arrive at a final, complete expression of HL7's vocabulary in MIF. |
| − | to arrive at a final, complete vocabulary | ||
Revision as of 20:49, 20 June 2014
One day soon, this page will document the VML Processing Widget. This an ANT-scripted process that:
- consumes proposals for change expressed in the HL7 Vocabulary Maintenance Language (VML),
- splits these proposals into two source streams targeted at the Access repository in which the HL7 Vocabulary content is stored::
- an SQL update stream for updating files of properties assigned to vocabulary objects, and
- an XML sream processed in Java to update the primary Access tables
- together, these streams update the vocabulary content stored in the Access repository,
- an SQL update stream for updating files of properties assigned to vocabulary objects, and
- uses a Java process to "clean up" the Access content,
- invokes RoseTree to express the complete vocabulary content in HL7 Model Interchange Format (MIF), and
- combines this MIF content from the Access repository with an externally maintained MiF extension file to arrive at a final, complete expression of HL7's vocabulary in MIF.
