Rex,
Very interesting. The EDXL-HAVE, EDXL-DE, and the EDXL-RM are all mentioned
in the National Emergency Communications Plan (NECP) on page 24, so we
should all be proud of that accomplishment. I do notice that the Common
Alerting Protocol (CAP) is not mentioned.
Tom Merkle
System Integration Analyst Sr. Staff
Lockheed Martin Corporation
Information Systems & Global Services - Intelligence
Telephone 410-298-2611
Mobile 410-409-9801
E-mail:
Web: www.lockheedmartin.com/gss
-----Original Message-----
From: Rex Brooks [mailto:]
Sent: Thursday, February 26, 2009 12:10 PM
To:
Cc: David RR Webber (XML)
Subject: [emergency] HITSP Dropping EDXL-HAVE? Fwd: [regrep] HHS and ebXML /
ISO15000
Importance: High
Hi Folks,
Below is the message I caught from David Webber on Sat. Jan. 24.
Sorry we didn't get back to this sooner, but we have all been busy.
The link in the message below, repeated here
<http://edocket.access.gpo.gov/2009/pdf/E9-1068.pdf>http://edocket.access.gp
o.gov/2009/pdf/E9-1068.pdf
downloads the pdf of the Federal Register entry in question.
I double checked and actually found a reference to (HAVE) without
EDXL at the bottom of column 1 and top of column 2 on page three:
"... The Interoperability Standards
associated with the HITSP
Biosurveillance Interoperability
Specification (HITSP v2 2007 IS02), or
''BIO,'' were recognized by the Secretary
in December 2007. The Hospital
Availability Exchange Standard (HAVE),
which was referenced in the HITSP
Interoperability Specification, was not
ready for secretarial recognition in June
2008 as anticipated, but since its
content has been previously included in
the accepted HITSP Interoperability
Specifications and it has achieved final
ballot by the Standards Development
Organization, it is being recognized. ..."
I don't know what the difference is between being recognized and
being accepted or listed.
It does not mention OASIS nor a full specification title, though it
does mention "... the Standards Development Organization," and it
says that has been accepted and it is being recognized even though it
wasn't ready in June 2008. However, it is not specifically listed as
the other OASIS standards are. For example EDXL-DE is listed as:
"... (OASIS) Emergency Data Exchange
Language (EDXL) Distribution Element
(DE) .."
EDXL-HAVE is also not found on the HITSP website for Biosurveillance
Standards
http://www.hitsp.org/InteroperabilitySet_Details.aspx?MasterIS=true&InteroperabilityId=49&PrefixAlpha=1&APrefix=IS&PrefixNumeric=02
among the specifications listed when you expand all versions, but is
included in the HITSP Acronyms.
Regardless, I think this should be made clear. The other issues also
remain, e.g. why have some standards been deleted and under what part
of their charter.
Cheers,
Rex
>Mailing-List: contact ; run by ezmlm
>List-Post: <mailto:>
>List-Help: <mailto:>
>List-Unsubscribe: <mailto:>
>List-Subscribe: <mailto:>
>Delivered-To: mailing list
>X-Originating-IP: 98.218.190.196
>From: "David RR Webber \(XML\)" <>
>To: " " <>
>Cc: , ,
> "Jamie Clark" <>
>Date: Sat, 24 Jan 2009 13:13:32 -0700
>Subject: [regrep] HHS and ebXML / ISO15000
>X-Nonspam: Statistical 61%
>
>Folks,
>
>What is going on here? Are vendors taking over the standard
>selection process within HHS?
>
>On Wednesday, HHS released for comment the health care
>interoperability standards; see
><http://edocket.access.gpo.gov/2009/pdf/E9-1068.pdf>http://edocket.access.g
po.gov/2009/pdf/E9-1068.pdf
>. There are a lot of references to HL7 and IHE standards, but ebXML
>Registry was specifically dropped; see page 4 (3602).
>
>Also - I believe HL7 has endorsed ebMS V3 - so this should be
>reflected in HHS too.
>
>Can we make official comments back to HHS from ISO and OASIS?
>
>Clearly with the number of European health organizations using ebXML
>messaging and Registry standards - HHS needs to be compatible with
>those partners systems - especially for delivery support to citizens
>overseas but also on basic information sharing levels - particularly
>for global epidemic and emergency management.
>
>Thanks, DW
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail. Follow this link to all your TCs in OASIS at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
