This was an old update that I wrote for my boss. I wrote it with as many acronyms and identifiers as possible just to test her :-)
Is everyone forced to work with this many TLA or is it just me?
Stepstone project's transition from the SODA subproject of Eclipse OHF
(moving to RT) to OHT is almost complete. We have been working on
support for the ISO/IEEE P11073-20601 PAN protocol and are slowly adding
support for the various 11073-104xx specializations. Most of this
support involves generating the java class model from the ASN.1 model
and adding support for the MDER encoding.
We have also
began work on a WAN interface prototype using WS-I Basic (SOAP/HTTP with
WS-Addressing) to send the XER encoded ASN.1 event reports from the AHD
to the RMS (WAN Device). As part of this work, we have analyzed some
other web service standards including WS-RX (WS-RM and WS-MC),
WS-Event/WS-Notification, WS-Man/WSDM, and others.
alternative being discussed in Continua is the re-purposing of the IHE
PCD protocol (HL7 V2.5 over MLLP--a TCP/IP protocol with some extra
Once the data arrives, it is up to
the RMS to translate these messages from the IEEE DIM model to HL7 RIM
in order to generate a CDA-based PHM (CCHIT approved?) and convert the
IEEE nomenclature to the various medical nomenclature standards like
SNOMED or LOINC. Once this is complete, the PHM is sent over the xHR
(x=PHR, EHR, EMR, etc) interface using IHE XDR or XDM (both from the XDS
family). If XDS is used instead, such as across a RHIO or HIE, we will
have to deal with handling patient IDs through profiles like IHE