PubMed Health⌕ Search

Biomedical subjects

Wes Rishel

Publications and source records attributed to Wes Rishel.

6 recordsLinked to original sources

Secure HL7 transactions using Internet mail (Internet draft).

The document describes the applicability of the Internet standardisation efforts on secure electronic data interchange (EDI) transactions for Health Level-7 (HL7), an EDI standard for Healthcare used world-wide. The document heavily relies on the work in progress by the IETF EDIINT working group. It is in most parts a restatement of the EDIINTs requirements document and application statement 1 (AS#1) tailored to the needs of the HL7 audience. The authors tried to make the document as self consistent as possible. The goal is to give to the reader who is not a security or Internet standards expert enough foundational and detail information to enable him to build communication software that complies to the Internet standards. Even though the authors rely on and promote the respective Internet standards and drafts, they did not withstand from commenting on and criticising the work where they see upcoming problems in use with HL7 or other EDI protocols that have not been in the initial focus of the EDIINT working group. The authors make suggestions to add parameters to the specification of the MIME type for EDI messages in RFC 1767 in order to enhance functionality. The authors give use cases for a larger subset of disposition types and modifiers of message disposition notifications. One key issue where the document goes beyond the current EDIINT drafts is the concept of non-repudiation of commitment to an EDI transaction. Secure EDI transactions should be regarded as "distributed contracts," i.e. not only the sending and receiving of single messages should be non-refutable but also the connection between messages interchanges. In anticipation of this requirement HL7 usually requires a response message to be sent to acknowledge every transaction. The authors therefore have the requirement to securely couple an EDI response message to its request message. Given the current shape of RFC 1767 this is generally possible only if a response message is coupled with an MDN receipt and the combination of both signed by the responder. The document describes a protocol to bundle MDN and response that uses the MIME multi-part/related content type in RFC 2112.

Computer Security↗

Federal health information policy: a case of arrested development.

Computerized patient records (CPRs) have reached a state of technical maturity that makes them an essential component of modern patient care. However, because uniform technical standards do not exist, CPRs constructed by different vendors do not convey clinical information easily from provider to provider. Moreover, unequal access to capital may mean a two-tier clinical information environment in the future. HIPAA, while important, did not anticipate the CPR revolution. New federal activism is required to assure not only interoperability of clinical data systems, but also that providers who lack capital and technical resources can make the needed digital conversion.

Ambulatory Care Information Systems↗

Exchanging health information: local distribution, national coordination.

The fragmentation of our health care system, our need to accommodate the diversity of existing health information exchanges, the lack of consistent implementation of clinical information standards, and the need to protect patients' privacy and maintain trust are all challenges to overcome in achieving broad-scale interoperable health information exchange. We propose several steps to coordinate information sharing among regional and other networks through universal adherence to a basic framework of policies and standards. The critical policy action is the identification of a "common framework" of standards and policies, maintained by a new Standards and Policy Entity that reflects both public- and private-sector participation.

Community Health Planning↗