Draftnotes from the Emergency Management Technical Committee (EM-TC) Meeting

Draftnotes from the Emergency Management Technical Committee (EM-TC) Meeting

Date: Oct 17,2017Next meeting: Oct 31, 2017

1. Attendance

A quorum was in attendance

1. Meeting notes. The notes from October 3were reviewed and after minor corrections, Scott made and Rex seconded a motion to approve. All agreed, no one abstained.

1. Notes from the Chair.
2. The Emergency Interoperability Consortium (EIC) meeting will be held 10/18, tomorrow from 2-4ET. The featured presentation is from FirstNet. Dial in details will be posted and all EMTC members are welcomed to attend.
3. Chet Ensign of OASIS TC Administration joined the meeting and was welcomed. He reviewed a copy of the CAP workshop report and wished to discuss with us the options OASIS has for the global term list. This has been an effort of the CAP SC since the previous workshop in Bangkok. While a thesaurus style format was agreed to, there remain a number of issues requiring the CAP community input before going forward. Chet saw how useful a global term list would be, and noted our issues. He offered that the TC could host an open source project to tap into the global community and work through the process. The OASIS open repository project is intended to do just that. The TC launches an open source project that anyone can join and participate in after signing a code license agreement. The TC choses an open source license when the project is formed. The TC then appoints the first maintainer. From that point on other maintainers can be added. I gave Chet some background on our effort. Rex offered that he has studied the github repository and now understand it fairly well. It would be a good way to gather opinions. A Committee Note (CN) could then be the documented event term list for publishing and the evolving list could be in the github. The master list would be kept at the open repo. Scott clarified that the github would be the living document where people could see where we are with it and the CN would be the published version. The maintainer role could be done by anyone (member or not). Github.com/OASIS-open. Chet pointed us to examples and noted the development of legal references, see TASC test assurance. Rex thinks we should consider this for documenting a vocabulary. The matter will be taken to the CAP SC for explanation and further discussion.
4. With Chet on the call, Rex took this opportunity to ask about the way we reference our standards and specifications. We would like to have a way for folks that are not conversant with all the iterations to be able to access latest version and associated artifacts. Rex suggested using an “*” to include those. Rex will write an email explaining the issue as it has been discussed in the RIM. Chet will plan to be available for the RIM call Nov 7.

1. Subcommittee (SC) Reports.
2. EDXL- Hospital Availability Exchange (HAVE). The public review period is over and Rex is working through the few comments. Scott is working on the Appendix that will include any mapping to Patient Administration data.
3. EDXL Reference Information Model (RIM) SC. With the events of the EDXL workshop, the RIM is considering recommending a restart of the Infrastructure SC to take comments on and further the work of the Distribution Element 2.0. There is some ongoing work on framework/toolkit to be considered to include a next version of ongoing review of EDXL family.

1. Adoption. No update, recent meetings have been cancelled. I noted that AWS contributed a higher resolution version of the CAP logo. I will post this on the Adoption site.

1. Adjourn. With our business complete, Rex made and Scott seconded a motion to adjourn. All agreed.

Respectfully submitted,

Elysa Jones Chair OASIS EM TC

Emergency Management Technical Committee