This wiki has undergone a migration to Confluence found Here
Difference between revisions of "January 25th, Templates Minutes"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
## Russell Hamm | ## Russell Hamm | ||
## Brett Essler | ## Brett Essler | ||
| + | ## Craig Parker (lurking) | ||
## | ## | ||
# Agenda Check | # Agenda Check | ||
| Line 25: | Line 26: | ||
# Action Items | # Action Items | ||
## ACTION: Can MIF represent co-ocurrance (invariants in openEHR) | ## ACTION: Can MIF represent co-ocurrance (invariants in openEHR) | ||
| + | ## ACTION: Russ and Brett to flush through DK's comments and make recommendations on adopting the CEN/openEHR requirements. | ||
| + | ## ACTION: Brett and Russ and Galen to put together tooling agenda items. | ||
| + | ## ACTION: Look at Patient Care RMIMs from William Goosen. | ||
# Adjourn | # Adjourn | ||
http://informatics.mayo.edu/wiki/index.php/January_25th%2C_Templates_Agenda | http://informatics.mayo.edu/wiki/index.php/January_25th%2C_Templates_Agenda | ||
Latest revision as of 16:34, 26 January 2006
- Roll Call
- Heath Frankel
- Galen Mulrooney
- Sarah Ryan
- Mark Shafarman
- Russell Hamm
- Brett Essler
- Craig Parker (lurking)
- Agenda Check
- Looks ok.
- Overview of the Phoenix WGM (minutes comming soon.)
- Heath's presentation and DMIM mapping
- CEN/openEHR Requirements
- Discussion on proceeding with CEN/openEHR/HL7 Archetypes Requirement adoption.
- HF - To take RMIM designer and output ADL would be reasonable. Modifying the Archetype editor to support HL7 artifacts would be a larger task. The Archetype Editor has builtin knowledge of CEN/openEHR classes that are used internalle. THese would need to be mapped.
- HF - Is it proper to build archetypes in the context of HL7 model?
- HF - ADL workbench is more generic. Displays nodes and branches. Can show the observation CMET in the ADL WB. Few ADL validators would handle HL7.
- HF - Can MIF handle the knowldge required by the invariants (co-occurance, interfield validation) How this can be extracted from MIF is not known.
- HF - Take WGs RMIMs, represent in Rose Tree, and export to ADL. Then ADL->OWL. These are supposed to be constraints on Clinical Statement, but no machinery to support.
- HF Australia developing Data Groups (on 11179) to support hierarchical structures (archetypes). Heath can put up in contact with the relevent people. One document (comprehensive) on medication datagroup.
- Review of MDE ProposalFile:MDEProposalv3sar123.docMDE Proposal
- Proposal for establishing a proof of concept for creating HL7 templates for a master set of data elements.
- Determine the next call time.
- Next Agenda Topics.
- Action Items
- ACTION: Can MIF represent co-ocurrance (invariants in openEHR)
- ACTION: Russ and Brett to flush through DK's comments and make recommendations on adopting the CEN/openEHR requirements.
- ACTION: Brett and Russ and Galen to put together tooling agenda items.
- ACTION: Look at Patient Care RMIMs from William Goosen.
- Adjourn
http://informatics.mayo.edu/wiki/index.php/January_25th%2C_Templates_Agenda
