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

Difference between revisions of "August 1, Minutes"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
## Joann Larson
 
## Joann Larson
 
# Agenda Check
 
# Agenda Check
##
+
## RH - Have Rachel give a review of Last Monday's Meeting.
 
# Review of last week's call (Rachel)
 
# Review of last week's call (Rachel)
 
## Try to combine info on CTS1 and expanding use cases of CTS2.
 
## Try to combine info on CTS1 and expanding use cases of CTS2.
Line 21: Line 21:
 
## RH - Section 1.3
 
## RH - Section 1.3
 
## RR - Add section 1.4 (constraints and boundaries.)
 
## RR - Add section 1.4 (constraints and boundaries.)
##
+
## Section 2 Business Senarios
## Russ to ask services group on how stringent we are holding to having a stakeholder for each use case / scenario.
+
### Russ Hamm
## Ask Services group about reformatting CTS R1 for submission of CTS 2.
+
### Harold Solbrig
##
+
### Joann Larson (when available)
##
+
## Section 3
#[http://hl7.org/library/committees/vocab/JKL%5FDraft%5FTerminology%5FConformance%5FCriteria%5FII%5F20050623%2Edoc EHR Functional Spec Terminology Requirements] (Joann Larson)
+
### Russ Hamm
 +
### Harold Solbrig
 +
### Joann Larson (when available)
 +
#### Russ to ask services group on how stringent we are holding to having a stakeholder for each use case / scenario.
 +
####Russ to ask services group on should these be formal use cases or story boards?
 +
#### Ask Services group about reformatting CTS R1 for submission of CTS 2.
 +
## Section 4 Relevant Standards and Reference Content
 +
### RH - From section 1ish, include CAP and SNOMED references.
 +
## Section 5 HL7 EHR Functional Model Traceability
 +
### Joann Larson
 +
## Section 6 Service definition and dependencies
 +
### Review and discuss next week.
 +
## Section 7 Detailed Functional Model for each Interface
 +
## Section 8 Use Scenario Interaction Details
 +
## Section 9 The Services Framework Functional Model
 +
## Section 10  Information Model and Semantic Binding Approach
 +
## Section 11  Recommendations for Technical RFP Issuance
 +
## Section 12  Assumptions
 
# Next Call Reminder
 
# Next Call Reminder
##
+
## Monday Aug 8th
 +
## Monday Aug 22nd
 
# Next Week's Agenda
 
# Next Week's Agenda
##
+
## Review of the Services Infrastructure responses.
 +
## Additions to the Document.
 
# Adjourn
 
# Adjourn
  
  
 
http://informatics.mayo.edu/wiki/index.php/August_1%2C_Agenda
 
http://informatics.mayo.edu/wiki/index.php/August_1%2C_Agenda

Latest revision as of 22:27, 1 August 2005

  1. Roll Call
    1. Russ Hamm
    2. Harold Solbrig
    3. Tony W.
    4. Rachel R.
    5. Tom Oniki
    6. Jim Obertholer.
    7. Joann Larson
  2. Agenda Check
    1. RH - Have Rachel give a review of Last Monday's Meeting.
  3. Review of last week's call (Rachel)
    1. Try to combine info on CTS1 and expanding use cases of CTS2.
    2. Rachel Started it, based on the HL7/OMG Draft specification Functional/Model.
    3. Decided to review the material on today's call.
  4. Service Functional Model Update (Russ/Rachel)
    1. Russ will post document on the Wiki
    2. Russ will coordinate changes to the document.
  5. Service Functional Model section assignments
    1. RH - Section 1.1, add in introduction a description of the relationship between CTS R1 and CTS R2.
    2. HS - Section 1.2, To flush out business case in further detail.
    3. RH - Section 1.3
    4. RR - Add section 1.4 (constraints and boundaries.)
    5. Section 2 Business Senarios
      1. Russ Hamm
      2. Harold Solbrig
      3. Joann Larson (when available)
    6. Section 3
      1. Russ Hamm
      2. Harold Solbrig
      3. Joann Larson (when available)
        1. Russ to ask services group on how stringent we are holding to having a stakeholder for each use case / scenario.
        2. Russ to ask services group on should these be formal use cases or story boards?
        3. Ask Services group about reformatting CTS R1 for submission of CTS 2.
    7. Section 4 Relevant Standards and Reference Content
      1. RH - From section 1ish, include CAP and SNOMED references.
    8. Section 5 HL7 EHR Functional Model Traceability
      1. Joann Larson
    9. Section 6 Service definition and dependencies
      1. Review and discuss next week.
    10. Section 7 Detailed Functional Model for each Interface
    11. Section 8 Use Scenario Interaction Details
    12. Section 9 The Services Framework Functional Model
    13. Section 10 Information Model and Semantic Binding Approach
    14. Section 11 Recommendations for Technical RFP Issuance
    15. Section 12 Assumptions
  6. Next Call Reminder
    1. Monday Aug 8th
    2. Monday Aug 22nd
  7. Next Week's Agenda
    1. Review of the Services Infrastructure responses.
    2. Additions to the Document.
  8. Adjourn


http://informatics.mayo.edu/wiki/index.php/August_1%2C_Agenda