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
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
 +
### 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. Also on should these be formal use cases or storyboeards?
 
## Ask Services group about reformatting CTS R1 for submission of CTS 2.
 
## Ask Services group about reformatting CTS R1 for submission of CTS 2.
 
##
 
##

Revision as of 21:00, 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
  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. Russ to ask services group on how stringent we are holding to having a stakeholder for each use case / scenario. Also on should these be formal use cases or storyboeards?
    7. Ask Services group about reformatting CTS R1 for submission of CTS 2.
  6. EHR Functional Spec Terminology Requirements (Joann Larson)
  7. Next Call Reminder
  8. Next Week's Agenda
  9. Adjourn


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