This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Templates September 2005 WGM Agenda"

From HL7Wiki
Jump to navigation Jump to search
 
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Templates Agenda for the September WGM. Suggestions:  
 
Templates Agenda for the September WGM. Suggestions:  
  
Monday
+
== Monday ==
Monday Q3 - Joint with MnM (MnM Hosting)  
+
=== Monday Q3 - Joint with MnM (MnM Hosting) === 
o Alignment between Archetypes and Templates. Goal: All projects (MnM Templates, Constraints, openEHR, etc.) should agree on the definitions, and overlap with openEHR.  
+
* Alignment between Archetypes and Templates. <p>
Monday Q4 - Joint with MnM (MnM Hosting)  
+
'''Goal''': All projects (MnM Templates, Constraints, openEHR, etc.) should agree on the definitions, and overlap with openEHR.
o MnM Template Specification (http://informatics.mayo.edu/wiki/index.php/Template_Specification)  
+
 
Tuesday
+
=== Monday Q4 - Joint with MnM (MnM Hosting)===
Tuesday Q1  
+
* MnM Template Specification http://informatics.mayo.edu/wiki/index.php/Template_Specification)
o Open  
+
* Atifacts in HL7 Templates Context. - Jane Currey
Tuesday Q2  
+
 
o Open  
+
== Tuesday ==
Wednesday
+
=== Tuesday Q1 ===
Wednesday Q1  
+
* Open  
o Strategize: How to involve HL7 TCs / SIGs in the Templates SIG. Many TCs and SIGs are currently developing domain specific models. Many of these models overlap significantly with the concept of Archetypes/Templates. How should we engage these TCs and SIGs to better understand their requirements?  
+
=== Tuesday Q2 ===
Wednesday Q2
+
* Open  
o Examine the Clinical Stmt model in terms of the constraints provided through openEHR object model.  
+
== Wednesday ==
• Wednesday Q3
+
=== Wednesday Q1 ===
o Open
+
* '''Update:''' TAAP. What example Templates have we collected to date?<p>
Wednesday Q4  
+
* How should we manage this collection in terms of
o Open  
+
** Extracting and managing requirements, ideas, and concepts.
Thursday
+
=== Wednesday Q2 ===
Thursday Q1  
+
* '''Strategize''': How to involve HL7 TCs / SIGs in the Templates SIG. Many TCs and SIGs are currently developing domain specific models. Many of these models overlap significantly with the concept of Archetypes/Templates. How should we engage these TCs and SIGs to better understand their requirements?  
o Joint with Vocabulary. Data elements, Vocabulary and Templates. Binding of vocabulary to models.
+
=== Wednesday Q3 ===
 +
* Examine the Clinical Stmt model in terms of the constraints provided through openEHR object model.  
 +
=== Wednesday Q4 ===
 +
* Open
 +
== Thursday ==
 +
=== Thursday Q1 - Joint with Vocabulary (Vocabulary Hosting) ===
 +
* Joint with Vocabulary, EHR, MnM. Data elements, Vocabulary and Templates. Binding of vocabulary to models.

Latest revision as of 16:55, 2 September 2005

Templates Agenda for the September WGM. Suggestions:

Monday

Monday Q3 - Joint with MnM (MnM Hosting)

  • Alignment between Archetypes and Templates.

Goal: All projects (MnM Templates, Constraints, openEHR, etc.) should agree on the definitions, and overlap with openEHR.

Monday Q4 - Joint with MnM (MnM Hosting)

Tuesday

Tuesday Q1

  • Open

Tuesday Q2

  • Open

Wednesday

Wednesday Q1

  • Update: TAAP. What example Templates have we collected to date?

  • How should we manage this collection in terms of
    • Extracting and managing requirements, ideas, and concepts.

Wednesday Q2

  • Strategize: How to involve HL7 TCs / SIGs in the Templates SIG. Many TCs and SIGs are currently developing domain specific models. Many of these models overlap significantly with the concept of Archetypes/Templates. How should we engage these TCs and SIGs to better understand their requirements?

Wednesday Q3

  • Examine the Clinical Stmt model in terms of the constraints provided through openEHR object model.

Wednesday Q4

  • Open

Thursday

Thursday Q1 - Joint with Vocabulary (Vocabulary Hosting)

  • Joint with Vocabulary, EHR, MnM. Data elements, Vocabulary and Templates. Binding of vocabulary to models.