[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] OASIS EDXL-HAVE v1.0 standard - comments and questions
-------- Original Message --------
Subject: [emergency] OASIS EDXL-HAVE v1.0 standard - comments and
From: "Gilmore, Timothy" <TIMOTHY.D.GILMORE@saic.com>
Date: Wed, November 26, 2008 9:30 am
Oasis members,I am writing this to address some issues I have found with the latest OASIS EDXL-HAVE v1.0 standard dated 1 November 2008. I have written some internal test procedures for the NIMS STEP program for vendors wishing to submit EDXL-HAVE related products as well as for their evaluation of NIMS concepts and principles. Here is a list of comments and questions I came across while putting together my test procedures:
- Page 10 shows the Document Object Model (DOM) and in various places it shows “Comment Text” as allowing for multiple instances as indicated with the asterisk (*). However, many places on the DOM don’t have the “Comment Text” element with the asterisk for “multiple instances allowed”. Is this an over site or should they be listed as they are (some with and some without) or one way or the other? The Supporting elements and types on page 60 show <have:CommentText> as OPTIONAL and not listed as “May use Multiple”. So this is a bit more confusing.
- Page 10 shows the DOM and under OrganizationInformation shows the CIQ supporting element “OrganizationInfo” which should be spelled as “OrganisationInfo”. The “z” should be an “s”.
- Page 10 under EmergencyDepartmentStatus shows only supporting element “CommentText” * which is listed on page 15 with other sub elements such as EMSTraffic, EMSCapacity, EMSCensus, EMSAmbulanceStatus, EMSAirTransportStatus. It seems that “CommentText doesn’t fit into the same categories as the other sub elements on the DOM. This is also more confusing.
- Page 10 under EMSTraffic, it lists sub elements EMSTrafficStatus, EMSTrafficReason. However, on page 15 it lists EMSTraffic with once again the confusing listing of “CommentText” which seems out of place or needs to be better described / documented.
- Page 16 indicates element <have:EMSCensus> with a “TriageCount” Type. This seems confusing again because the DOM on page 10 shows “TriageCount” as an element.
- Page 10 under EMSAmbulanceStatus does not list “CommentText” as it does on page 19/20 as a sub element. Again confusing.
- Page 10 under Offload does not have any supporting element documentation on what I would expect to see it listed on page 20 as an element and not a Type. This would relate to elements <have:EMSOffloadStatus> and <have:EMSOffloadMinutes>. Confusing to figure out.
- Page 22 shows element <have:HospitalbedCapacityStatus> with sub element “BedType”, yet page 10 on the DOM it indicates a sub element of “CommentText”. Confusing.
- Page 10 under ServiceCoverageStatus does not indicate a complete list of sub elements. On page 29 there are many more not listed on the DOM (page 10).
- Page 36 lists <have:OBGYN> and the listing is identical to <have:OBGYNWithLaborDelivery>. How does one know when to use one vs the other if they are identically listed?
- Many places in the document list “Surgery Services” and also lists “Surgical Services” interchangeably. For consistency sake, make them one or the other.
- Page 60 lists element <have:LastUpdateTime> as Required. Is this Required once only, Multiple use or Conditional? The constraint listed would seem to indicate this should be listed as Conditional.
- CIQ elements on page 62 to 69 do not use the standard element format of <have:elementname> but instead leave out the <have: >. Is this correct?
Thank you for reading my concerns for these issues.
NIMS STEP Test and Evaluation Engineer