Archive for the ‘HITSP’ Category

Titanic Still Teaching us Lessons about Regulations

Friday, April 13th, 2012

By MICHAEL ARRIGO

The Titanic is still teaching us lessons.  Titanic’s history is often retold inaccurately with regard to safety equipment.  For example, many believe that short sightedness and greed of the builders led to the shortage of lifeboats.  For the April 15th 2012 100th anniversary of the sinking of Titanic,  The Wall Street Journal took a different view in the article, “The Real Reason for the Tragedy of the Titanic“  The Journal noted that popular beliefs about the shortage of lifeboats due to cost or aesthetics weren’t correct.  Rather, outdated government regulations were to blame.  I considered the possibility that the regulatory failure that contributed to the Titanic sinking high loss of life could provide us with a lesson about health care regulations.

“This is a distressingly common problem. Governments find it easy to implement regulations but tedious to maintain existing ones—politicians gain little political benefit from updating old laws, only from introducing new laws.” – Wall Street Journal

British Board of Trade required vessels above 11,023 U.S. tons to carry 16 lifeboats. Titanic exceeded the requirements by four boats. But the ship was 46,328 tons. The Board hadn’t updated its regulations for nearly 20 years.  Chris Berg of WSJ writes that Titanic builders and designers complied with the regulatory standard of the day.  The builders tested the Transportation board “…to see whether regulators required it…” to add more lifeboats.   WSJ concludes, “Titanic’s chroniclers put moral narrative ahead of a historical one.  … British regulators assumed responsibility for lifeboat numbers and then botched that responsibility…it is hard not to see the Titanic disaster as a tragic example of government failure.”

In healthcare, politicians legislated the American Recovery and Reinvestment Act (ARRA), the HITECH Act, and the Patient Protection and Affordable Care Act (PPACA). But the responsibility to update the requirements about how HIT systems will support these mandates is held by the Office of the National Coordinator (ONC) for health and human services (HHS).  Each regulation has an extensive list of compliance requirements.

To monitor the effectiveness of these measures, we need to be collecting the right data and by analyzing the data, make course corrections when appropriate.  But the technology specifications supporting PPACA comparative effectiveness and payment reform aren’t working yet and fall short.  Few are looking closely and asking questions regarding how this technology actually supports the intent of the mandates.

Stage 2 Meaningful Use is available for public comment, but there is no information on how the interoperability standards truly collect, store and enable analysis of the right data. Illuminating this issue, I discovered that ONC Clinical Document Architecture (CDA) isn’t mature enough to specify the capture and sharing of data beyond an “encounter” or single visit of a patient by a health care provider.  There is a noble name for the current standard, a “Continuity of Care Document” or CCD.  But to truly measure effective health care, we have to measure patient wellness and track treatments over time, (“longitudinal patient records” as healthcare experts call it).  The data must be aggregated and shared in health information exchanges (HIEs) that span the continuum of care, geographies, and disparate health IT systems such as multi-vendor electronic medical records, and of course across health care providers.  The CCD standard of today doesn’t do that.  Just as the British Trade Board’s outdated regulations weren’t designed to comprehend a ship so large, the CCD isn’t designed for the larger vision of capturing enough data to measure patient health over time.

Are you surprised? I was.  If you are interested in the technical details, see this link from the web site Model-Driven Health Tools (MDHT) for CDA wherein the CCD specification clearly states regarding an Encounter, “…Shall contain exactly one…“  Make sure to search for “Encounter.”  Below is a screen shot of the document.  You’ll see the HL7, IHE, and HITSP references – these are all bodies involved with setting the standard.   This is despite the fact that the CDR in the introduction states, “…The CCR is a core data set of the most relevant administrative, demographic, and clinical information facts about a patient’s healthcare, covering one or more healthcare encounters…”

Continuity of Care Document Specification

Continuity of Care Document Specification

Almost everyone who studies the problem agrees that longitudinal health records are beneficial, but as I look into how HHS and various standards groups within healthcare are hoping to do this, there are gaps that aren’t being addressed.  To accomplish that goal, ONC / HHS should continue the dialogue with commercial health IT companies, providers and health plans need to iterate these specifications.  The development of a standard, sharable digital XML file as a longitudinal data container, supported by electronic medical records, shared in HIE clinical networks could provide the data we need.   Just as Titanic’s vision was larger than the regulations of her day,  today we have a static standard born from regulations that won’t address the bigger vision we plan to build in healthcare.  We need to create a broader more innovative vision for continuity of care CCDs.  Defining the standard and implementing it will be  hard work that is probably best done by a small team of dedicated individuals that represent a cross-section of the health care economy.

Michael Arrigo is Managing Partner of No World Borders’ health care practice.

Share

HIT Policy and Standards Committees Commence Work on National Health Information Infrastructure HITSP

Wednesday, June 10th, 2009

HIT Policy and Standards Committees Commence Work on National Health Information Infrastructure HITSP (Health Information Technology Standards) updated to the National eHealth Collaborative in early June 2009. Here are a few highlights:

HITSP has moved rapidly to focus on meaningful use and ARRA‘s 8 priorities:
1. Encourage technology that protects the privacy of health information
2. Nationwide health information technology infrastructure
3. Utilization of a certified electronic record for each person in the US by 2014
4. Technologies that support accounting of disclosures made by a covered entity
5. Electronic records to improve quality
6. Technologies that enable identifiable health information to be rendered unusable/unreadable
7. Demographic data collection : race, ethnicity, primary language, and gender
8. Technologies that address the needs of children and other vulnerable populations

HITSP has embraced a service-oriented architecture, which enables reuse of capabilities instead of requiring new value cases for each novel requirement. Initial services include:
• Issue Ambulatory Prescriptions
• Query for Medication History
• Communication of Structured Documents
• Communication of Unstructured Documents
• Clinical Referral Request
• Retrieval of Medical Knowledge
• Return Laboratory Results Message
• Communication of Laboratory Reports
• Communication of Imaging Information
• Quality Measures for Hospital based Quality Information Collection and Reporting
• Quality Measures for Clinician Quality Information Collection and Reporting
• Immunization Registry Update
• Immunization Registry Query
• Communication of Immunization Documents
• Vaccine and Drug Inventory Reporting
• Public Health Case Reporting
• Emergency Common Alerting
• Send and Receive Relevant BioSurveillance Data
• Communicate Resource Utilization
• Exchange Administrative Benefits/Eligibility Transactions
• Exchange Administrative Referral/Authorization Transactions
• Provider Directory

HITSP is moving to an electronic publication approach for all its implementation guidance.

HITSP has embraced USHIK as a repository for its harmonized standards and code sets

The July 15 deliverables will directly support the needs of the HIT Standards Committee and its workgroups to identify standards, implementation guidance, and certification criteria in support of meaningful use.

Share