1 / 29

Copenhagen Fire Brigade The 112 Group

MayDayML. Emergency Data Exchange - Proposal to PSPP SSG SA. Jens C. Behrens , Ph.D.E. jens@behrens.cc - behrens@112.dk. Copenhagen Fire Brigade The 112 Group. MayDayML. The need to standardize. Increased use of computer systems Proprietary systems Babel Syndrome

kostya
Télécharger la présentation

Copenhagen Fire Brigade The 112 Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MayDayML Emergency Data Exchange - Proposal to PSPP SSG SA Jens C. Behrens, Ph.D.E. jens@behrens.cc - behrens@112.dk Copenhagen Fire Brigade The 112 Group

  2. MayDayML The need to standardize • Increased use of computer systems • Proprietary systems • Babel Syndrome • Transfers are labor intensive/expensive to implement • Changes must occur simultaneously • Transfer errors = “No-mans land” Results of standardization • More accurate communications • Open competition among software suppliers • Less expensive and more reliable systems Copenhagen Fire Brigade The 112 Group

  3. MayDayML Babel Syndrome Examples: Addresses H.C.Andersens Boulevard / H C Andersens Boulevard Bylowsvej / Bülowsvej Stations Gentofte / Glostrup / Gladsaxe - G/GT/GL/GO etc. Frederiksberg - FRB / FB / fB / F - Fælledvej Vehicle Types Pumps (sprøjte) - SP/MO Hospitals Rigshospitalet RH/RIGS Copenhagen Fire Brigade The 112 Group

  4. MayDayML The need to standardize • Increased use of computer systems • Proprietary systems • Babel Syndrome • Transfers are labor intensive/expensive to implement • Changes must occur simultaneously • Transfer errors = “No-mans land” Results of standardization • More accurate communications • Open competition among software suppliers • Less expensive and more reliable systems Copenhagen Fire Brigade The 112 Group

  5. MayDayML Why XML ? • Open standard (W3C) • Fixed format exchange is obsolete • Virtually unlimited scalability • Piecewise data updates • Legible to humans • XML documents are easy to create • Free parsers available on many platforms www.xml.com Copenhagen Fire Brigade The 112 Group

  6. MayDayML MayDayML scope Level 0 Alarm Sources MDML 01 MDML 10 Level 1 Emergency Call-taking MDML 11 MDML 12 MDML 21 MDML 13 MDML 31 MDML 22 Level 2 Emergency Dispatch & Control MDML 23 MDML 32 Level 3 Hospital Emergency sector MDML 33 Copenhagen Fire Brigade The 112 Group

  7. MayDayML eXtensible Markup Language <Tag1> <Tag2>info</Tag2> <Tag3 Attribute1 = ”AttrInfo”>info</Tag3> <Tag4>info</Tag4> <Tag4>more info</Tag4> </Tag1> • Document Type Definition, can be ISO 9070 registered Copenhagen Fire Brigade The 112 Group

  8. MayDayML An Initial example: MDML12 – Call-taking to Dispatch General issues GIxxx: Area specific issues Inn-xxx: where nn is the area and xxxis an incremental unique number. Copenhagen Fire Brigade The 112 Group

  9. MayDayML GI001: General naming conventions for all tags across all MDMLnn should be decided Name • All tags must have a capitalized first letter. • The first letter of a word must be capitalized. • The word Number will always be shortened to No. • The word Reference will always be shortened to Ref • Yes = Y, No = N etc. • Identical data-items in different MDML areas should • always have the same tag. VehicleNo RefNo GI002: Is this a desirable convention ? If so, how could this be assured ? Copenhagen Fire Brigade The 112 Group

  10. MayDayML Emergency tag:<Emergency> I12-001: What areas of communication from call-taking to dispatch should be covered by MDML12 Emergency.RefNo unique number for future reference Emergency.Org (Org for Organization) unique within a country Emergency.Country <Emergency Country="DK" Org="112" RefNo="1120001"> GI003: A national body must be set up to handle the assignment of unique numbers to parties wanting to utilize MDML Copenhagen Fire Brigade The 112 Group

  11. MayDayML Emergency.Type, eg. 1=Fire 2=Rescue, 3=Ambulance, 4= Pollution I12-002: Standardization of Type Emergency.Driving, eg. 1=Acute, Lights and horns, 2=immediate, no lights I12-003: Standardization of Driving Emergency.StartTime, eg. yyyymmdd hhmmss GI004: Standardization of date/time format Copenhagen Fire Brigade The 112 Group

  12. MayDayML Emergency.Reduced as yes/no Emergency.Doctor as yes/no I12-004: Decision on additional attributes for the emergency tag <Emergency Country="DK" Org="112" RefNo="1120001" Type="3" Driving="1" StartTime="19991108 121110" Reduced="N" Doctor=”Y”> Copenhagen Fire Brigade The 112 Group

  13. MayDayML The person tag:<Person>Name</Person> Person.CPR ,central personal registration number or similar. Should be encrypted. Person.Sex male/female (M/F) GI005: Encryption scheme and implementation for sensitive MDMLnn data items I12-005: Decision on additional attributes for the Person tag <Person CPR="123456-1243" Sex="M"> Jens C. Behrens</Person> Copenhagen Fire Brigade The 112 Group

  14. MayDayML The street tag :<Street>StreetName</Street> Street.RefNo, an official unique number designating the street Street.BuildingNo, Street number Street.Story, Indication of story if avilable Street.Map, Map name Street.MapCoor, Map coordinates I12-006: Standardization of Street.RefNo I12-007: Standardization of Street.BuildingNo I12-008: Standardization of Street.Story I12-009: Standardization of Street.Map map names and coordinates I12-010: Decision on additional attributes for the Street tag <Street RefNo="1001" BuildingNo="23" Story="1.th" Map=”KRAK” MapCoor="148 F5"> H.C.Andersens Boulevard</Street> Copenhagen Fire Brigade The 112 Group

  15. MayDayML Additional address information:<AddStreetInfo> Ind i gården ved trappe B</AddStreetInfo> I12-011: Decision on additional attributes for the AddStreetInfo tag The phone number of the caller: <Phone>Phone number</Phone> Phone.Area, area code I12-012: Decision on additional attributes for the Phone tag <Phone Area="+45">33664933</Phone> Copenhagen Fire Brigade The 112 Group

  16. MayDayML The municipality in which the emergency occurred: <Municipality>Name</Municipality> Municipality.RefNo, an official unique number designating the municipality I12-013: Standardization of Municipality.RefNo I12-014: Decision on additional attributes for the Municipality tag <Municipality RefNo="101">København</Municipality> Copenhagen Fire Brigade The 112 Group

  17. MayDayML Third parties may need to be informed: <Inform>3rd party</Inform> Inform.Done, Call-taker has already informed the 3rd party, Yes/No I12-015: Standardization of 3rd party identification I12-016: Decision on additional attributes for the Inform tag <Inform Done="Y">Politiet</Inform> Copenhagen Fire Brigade The 112 Group

  18. MayDayML Diagnosis tag:<Action>Diagnosis</Action> Action.Code, a unique pair referencing specific diagnosis I12-017: Standardization of Action.Code I12-018: Decision on additional attributes for the Action tag <Action Code="08,25"> Stærkt chokeret/Alkoholforgiftet</Action> Copenhagen Fire Brigade The 112 Group

  19. MayDayML Desired vehicle(s):<Vehicle></Vehicle> Vehicle.Level, a number signifying the role of the vehicle, eg. 1=primary, 2=secondary etc. Vehicle.Type, type of vehicle desired, eg. Ambulance=”A” Vehicle.Station, home location of desired vehicle Vehicle.VehicleNo, vehicle specific id number I12-019: Standardization of Vehicle types I12-020: Standardization of Location reference to stations I12-021: Standardization of Specific vehicle ID numbers I12-022: Decision on additional attributes for the Vehicle tag <Vehicle Level="1" Type="A" Station="H" VehicleNo="1"/> <Vehicle Level="2" Type="A" Station="C"></Vehicle> <Vehicle Level="1" Type="LA" Station="KH" VehicleNo="1"> </Vehicle> Copenhagen Fire Brigade The 112 Group

  20. MayDayML Comment to the incident:<Comment>text</Comment> I12-023: Decision on additional attributes for the Comment tag <Comment>Pt. virker 08 med trang til 25</Comment> Copenhagen Fire Brigade The 112 Group

  21. MayDayML <!--TEST DOCUMENT All Elements--> <Emergency Country="DK" Org="112" RefNo="1120001" Type="2" Driving="1" StartTime="19991108 121110" Reduced="N" Doctor="Y"> <Person CPR="123456-1243" Sex="M">Jens C. Behrens</Person> <Street RefNo="1001" BuildingNo="23" Story="1.th" Map=”KRAK” MapCoor="148 F5">H.C.Andersens Boulevard</Street> <AddStreetInfo>Ind i gården ved trappe B</AddStreetInfo> <Phone Area="+45">33664933</Phone> <Municipality RefNo="101">København</Municipality> <Inform Done="Y">Politiet</Inform> <Inform Done="N">Belysningsvæsnet</Inform> <Action Code="08,25">Stærkt chokeret/Alkoholforgiftet</Action> <Vehicle Level="1" Type="A" Station="H" VehicleNo="1"></Vehicle> <Vehicle Level="2" Type="A" Station="C"></Vehicle> <Vehicle Level="1" Type="LA" Station="KH" VehicleNo="1"/> <Comment>Pt. virker 08 med trang til 25</Comment> </Emergency> Copenhagen Fire Brigade The 112 Group

  22. MayDayML Issues GI001: General naming conventions for all tags across all MDMLnn should be decided GI002: Same tag-names accross all MDMLnn ? If so, how could this be assured ? GI003: A national body must be set up to handle the assignment of unique numbers to parties wanting to utilize MDML. GI004: Standardization of date/time format. GI005: Encryption scheme and implementation for sensitive MDMLnn data items Copenhagen Fire Brigade The 112 Group

  23. MayDayML I12-001: What areas of communication from call-taking to dispatch should be covered by MDML12 I12-002: Standardization of Type I12-003: Standardization of Driving I12-004: Decision on additional attributes for the emergency tag I12-005: Decision on additional attributes for the Person tag I12-006: Standardization of Street.RefNo I12-007: Standardization of Street.BuildingNo I12-008: Standardization of Street.Story I12-009: Standardization of Street.Map map names with respective coordinates I12-010: Decision on additional attributes for the Street tag I12-011: Decision on additional attributes for the AddStreetInfo tag Copenhagen Fire Brigade The 112 Group

  24. MayDayML I12-012: Decision on additional attributes for the Phone tag I12-013: Standardization of Municipality.RefNo I12-014: Decision on additional attributes for the Municipality tag I12-015: Standardization of 3rd party identification I12-016: Decision on additional attributes for the Inform tag I12-017: Standardization of Action.Code I12-018: Decision on additional attributes for the Action tag I12-019: Standardization of Vehicle types I12-020: Standardization of Location reference to stations I12-021: Standardization of Specific vehicle ID numbers I12-022: Decision on additional attributes for the Vehicle tag I12-023: Decision on additional attributes for the Comment tag Copenhagen Fire Brigade The 112 Group

  25. MayDayML MDML12 DTD Example The DTD (Document Type Definition) represents the syntax of an XML document used by the XML parser to parse the XML document I12-024: Decision on minimal content of a MDML12 document Example decision: Allow any field except the Emergency.RefNo to be optional Copenhagen Fire Brigade The 112 Group

  26. MayDayML MDML12 DTD Example <!--MayDayML12 test DTD--> <!ELEMENT Emergency (Person*, Street*, AddStreetInfo*, Phone* , Municipality*, Inform*, Action*, Vehicle*, Comment*) > <!ATTLIST Emergency RefNo CDATA #REQUIRED Type CDATA "" Driving (1|2|3|4|5) "" StartTime CDATA "" Reduced CDATA "" Doctor CDATA “”> <!ELEMENT Person (#PCDATA)> <!ATTLIST Person CPR CDATA "" Sex (M|F) ""> <!ELEMENT Street (#PCDATA)> <!ATTLIST Street RefNo CDATA "" BuildingNo CDATA "" Story CDATA "" Map CDATA "" MapCoor CDATA “”> Copenhagen Fire Brigade The 112 Group

  27. MayDayML MDML12 DTD Example, continued <!ELEMENT AddStreetInfo (#PCDATA)> <!ELEMENT Phone (#PCDATA)> <!ATTLIST Phone Area CDATA ""> <!ELEMENT Municipality (#PCDATA)> <!ATTLIST Municipality RefNo CDATA ""> <!ELEMENT Inform (#PCDATA)> <!ATTLIST Inform Done (Y|N) "N" Phone CDATA ""> <!ELEMENT Action (#PCDATA)> <!ATTLIST Action Code CDATA ""> <!ELEMENT Vehicle EMPTY> <!ATTLIST Vehicle Level CDATA "" Type CDATA "" Station CDATA "" VehicleNo CDATA ""> <!ELEMENT Comment (#PCDATA)> Copenhagen Fire Brigade The 112 Group

  28. MayDayML A Programmers Perspective XML parsers are available, see eg.www.xml.com Result of parsing is accessible thru the Document Object Model DOM XML documents may be generated thru DOM object manipulation An easy alternative is simple formatting of existing data IE5.0 parser demo Copenhagen Fire Brigade The 112 Group

  29. MayDayML For less expensive, more reliable, more flexible communication in the Emergency arena Copenhagen Fire Brigade The 112 Group

More Related