Iepd analyze Requirements Use Cases for edxl situation reporting messages Draft Version 4



Download 212.64 Kb.
Page1/3
Date31.01.2017
Size212.64 Kb.
  1   2   3



IEPD Analyze Requirements

Use Cases

for

EDXL Situation reporting messages

Draft Version 1.4

Prepared by the SWG EMS Call scenario team
(Scenario version 3.4)


EDXL “Situation Reporting” draft Messaging Standard

September 21, 2007

Revision / initial Meeting History


Name

Date

Reason For Changes

Version

Tim Grapes

April 2007

Highway Incident Scenario team kickoff meeting. Materials provided as input to develop scenario

Scenario 0.0

Tim Grapes

5/7/07

Presentation provided on DM program and EDXL messaging standards initiatives – call for scenario team volunteers

Scenario 0.0

Tim Grapes

6/01/07

EMS Call scenario team kickoff – Existing scenario identified as a starting point for tailoring

Scenario 3.0

Elizabeth Sullivan

6/11/07

Elizabeth tailored the scenario for realism and removing futuristic topics and technologies

Scenario 3.1

Tim Grapes

7/2/07

Tim incorporated Elizabeth’s revisions into the actual document using word “track changes” (version 3.1); put in standard scenario format, and then made additional revisions to transform some of the network and communications terms into “information exchange” terms (version 3.2).

Scenario 3.2

Larry Williams & Kevin McGinnis

7/4/07

Additional scenario tailoring and editing

Scenario 3.3

Tim Grapes

7/19/07

Following the 7/12 team review of the scenario, revised scenario to version 3.4 per walk-through comments and those provided by Kevin McGinnis. In the separate Use Case Document (“EDXL_use_case_EMS_Callv1.0.doc “) broke out the textual scenario into Tabular format with an independent row for each activity or event, columns for sequence, date/time, and Activity/event, and added Use Case Chronology columns for Senders, Recipients, and Information-Sharing requirement

Scenario 3.4 & U.C. (use case) 1.0

Tim Grapes

8/2/07

Scenario team meeting conducted – information and revisions from the call incorporated

U.C. 1.1 & UC 1.2

Jeff Sexton and Tim Grapes

8/15

Jeff Sexton incorporated revisions and additional steps, and Tim incorporated other revisions from previous call

U.C. 1.3

Tim Grapes

8/28 – 9/121 2007

A meeting was held on 8/28. Revisions from that meeting are incorporated into this version and distributed for review on 9/21/07

U.C. 1.4


Participants


Name

Organization / Profession

Email

Copeland, Tommy

Putnam County EMS
Cookeville, TN
Healthcare IT Stds Panel (HITSP)

tcopeland@putnamco.org

Irby, Robert

EMS, Oklahoma State Dept. of Health

RobertI@health.ok.gov

Mann, Clay

Utah.edu, EMS, HITSP

clay.mann@hsc.utah.edu

McGinnis, Kevin

PSG, Vice-Chair (NASEMSO) State EMS Officials, (JNEMSLC) Joint National Emergency Medical Services Leadership Conference

mcginnis@nasemsd.org; k.mcginnis@adelphia.net

Porter, Randy

Putnam County EMS
Cookeville, TN
Healthcare IT Stds Panel (HITSP)

rporter@putnamco.org

Rogers, Shawn

Director, Emergency Medical Services Division,

The Oklahoma State Department of Health



ShawnR@health.ok.gov

Schilling, Roger

EMS, Oklahoma State Dept. of Health

RogerS@health.ok.gov

Sexton, Jeff

Tennessee Department of Health, BHLR Information Technology Services, Healthcare IT Stds Panel (HITSP)

Jeff.Sexton@state.tn.us

Sullivan, Elizabeth

EMS, Oklahoma State Dept. of Health

ElizabethS@health.ok.gov

Vandame, Richie

Corrections Officer / former parametic supervisor

Richard.Vandame@dhs.gov

Williams, Larry

President / CEO, Roadside Telematics Corporation, HITSP

lwilliams@roadmedic.com



Directory: committees -> download.php
download.php -> Emergency Interoperability Consortium Membership Meeting
download.php -> Technical Communicators, Get ready: Here comes Augmented Reality! Rhonda Truitt
download.php -> Oasis set tc
download.php -> Technical Committee: oasis transformational Government Framework tc chair
download.php -> Ibops protocol Version 0 Working Draft 2 9 March 2015 Technical Committee
download.php -> Reliability of Messages Sent as Responses over an Underlying Request-response Protocol
download.php -> Service Component Architecture sca-j common Annotations and apis Specification Version 1 Committee Draft 03 – Rev1 + Issue 127
download.php -> Scenario Two – Hurricane Warning
download.php -> Technical Committee: oasis augmented Reality in Information Products (arip) tc chairs
download.php -> This is intended as a Non-Standards Track Work Product. [Type the document title]


Share with your friends:
  1   2   3


The database is protected by copyright ©ininet.org 2019
send message

    Main page