Perficient Healtchare Solutions Blog

Subscribe via Email

Subscribe to RSS feed

Perficient Healthcare Business Solutions

Perficient Healthcare on Twitter

avatar

Michael Planchart

Posts by this author:

avatar

The ABCs of the CCD – Part I of III

by on April 25th, 2012

CCD is an acronym that stands for “Continuity of Care Document”.  The CCD is a file that uses Extensible Markup Language (XML) format, which could have one of 3 different structure levels.  I will explain the various structure levels in Part III of this blog series.  A CCD contains patient related information that could be electronically exchanged between healthcare providers, as well as, shared with the patients themselves.

The CCD template, derived from the American Society for Testing and Materials (ASTM) Continuity of Care Record template or ASTM E2369-05 Standard Specification, or simply stated the CCR.  The CCD is constrained by the HL7 (Health Level Seven) Clinical Document Architecture (CDA).  The CDA adheres to the HL7 V3.0 Reference Information Model or RIM.

The ASTM CCR was created to provide a snapshot in time that contains a summary of relevant and pertinent encounters information (e.g., demographic, clinical, financial) of a patient.

Health Level Seven International partnered with ASTM to create an HL7 version of the CCR for institutions that preferred using the CDA model, hence the birth of the CCD.  The CCD maps the CCR elements into the CDA structure.

The CCD is a template based on the principles of the HL7 CDA.  The characteristics of a clinical document based on the CDA are the following:

  • Persistent
  • Authenticable
  • Human readable
  • Self-context
  • Thorough and complete
  • Stewarding

Although one of the characteristics of a CCD is to be human-readable this does not mean that there isn’t a tool involved for the readability.  A CCD could be rendered with a simple web browser in order to comply with the human-readability qualification.

The CCD is structured as a CDA document.  For those of you familiar with XML documents the following line-by-line depiction will be easily understood:

  • Document
    • Header
      • Body
        • Sections
          • Optional narrative block
            • Entries

A CCD includes the following 16 sections:

  1. Family history
  2. Social history
  3. Functional status
  4. Allergies
  5. Immunizations
  6. Medications
  7. Vital signs
  8. Medical equipment
  9. Support
  10. Encounters
  11. Problems
  12. Procedures
  13. Results
  14. Plan of care
  15. Payers
  16. Advance directives

Many Electronic Health Record (EHR) vendors are starting to implement the CCD to share patient information across Health Information Exchanges(HIEs), outpatient centers and other clinical providers.

The CCD is not alone.  There are many other CDA based templates:

  • Discharge summaries,
  • History and Physical (H&P)
  • Procedure Note
  • Progress Note
  • Operative Note
  • Consultation Note
  • Diagnostic Imaging Report

In the next Part II of this series we will explore a “real-world” example of a CCD.

avatar

Facing and Overcoming the 2012 #HealthIT Challenges Amidst the End of the World – Part 2 of 2

by on February 23rd, 2012

In the first post of this 2 part blog we explored the big challenges with the demands that the ARRA HITECH and other compliance and regulatory impositions have impacted Healthcare IT: HIPAA’s Version 5010 conversion, ICD-10 migrations, Meaningful Use of EHRs and their Attestation and Accountable Care Organizations.  We also briefly touched the popular topic of the imminent end of the world in 2012 according to the Mayan calendar prediction.

If you read carefully you would have noticed that my predictions, well, they have some small glitches now and then, or you may call them “bugs” due to my software developer background.  So at the end of this blog we’ll have to revisit the end of the world prediction.  Sorry folks.

The ICD-10 deadline, as of last week, was announced by the HHS Secretary Kathleen G. Sebelius the intent to delay the compliance date.  Hopefully the delay will not be such that it has a big impact on healthcare interoperability projects.  ICD-10 would help the way healthcare data is stored and exchanged between systems.  One of the drawbacks of ICD-9 is that since it lacked codes to describe many diagnosis or procedures clinicians and related clerical staff would use the code that closely matched the reimbursement amount expected.  Pro-active healthcare organizations should move forward with their ICD-10 conversion projects since it solves many inherent problems contained in their data that hinders interoperability in a meaningful way.

Data Aggregation and Mining for Successful Quality Measurement Reporting and Performance Improvement Requirements

Going back to the topics we left off in our previous post, I would like to dive a little into data aggregation.  Healthcare data is contained in many source systems inside a hospital organization and more frequently it can be found outside of the organization.  I have been in several projects where I’ve had to aggregate data located in 3 different states in the US!

If your organization plans to successfully meet Meaningful Use stages 1, 2 and 3 then getting control of your data is of paramount importance.  Meaningful Use stage 1 may appear to be trivial to many organizations but don’t let this mislead you as to the growing complexities of stages 2 and 3.  Albeit we don’t know the details of the requirements for stage 2, which are to be announced shortly, what we do know is that they will require more data from the different source systems.

Health BI, as an aggregation platform, can receive healthcare data from myriad sources; whether it’s from the inpatient Health Information System (HIS) , the outpatient Electronic Medical Record (EMR) or the Laboratory Information System (LIS) it can all come together in a single repository from which up to 600 Clinical Quality Measures can be reported!  Health BI is modeled after the HL7 v3.0 RIM.

(more…)

avatar

Facing and Overcoming the 2012 #HealthIT Challenges Amidst the End of the World – Part I of 2

by on February 2nd, 2012

Background

Healthcare providers and eligible primary physician practices are undergoing analysis paralysis because of all the government impositions on improving healthcare with the following list of complex problems to solve: HIPAA’s Version 5010 conversion, ICD-10 migrations, Meaningful Use (MU) of EHRs and Attestation , Accountable Care Organizations (ACOs) , Data Aggregation and mining for successful Quality Measurement Reporting and Performance Improvement Requirements, CPOE implementations, CDA and the CCD template based document generation for sharing patient information between health providers, Natural Language Processing (NLP), Private Health Information (PHI) in the Cloud, internal demand for emerging technologies, the Mayan prediction of the end of the world, Et cetera, Et cetera, Et cetera.

The list above is not a bloated aggregation of current buzz-words, terms, solutions and a potential world event, but actually projects (challenges) that most healthcare providers, large and small, have had to embark on or are getting ready to do so beginning the first quarter of this year; yes indeed, that is NOW!

The aforementioned list isn’t exhaustive either, because there are other very specialized areas that the ARRA/HITECH and the Affordable Care Act have intentionally or unintentionally triggered off as well.  We will leave a discussion of this topic to another blog in the near future.

Those organizations that have been proactive and early starters or pioneers have a clear advantage over the others but yet they’ll still face their own challenges and probably very similar to the late bloomers.

Any of these challenges (which are also projects by nature) involve not only unique but also many common complexities such as:

Format:        Challenge Level of Effort (1 = Least – 5 = Most)

  • Stakeholder alignment 2
  • Project Management 2 (communication, charter, schedule, resources, Et cetera)
  • Multiple vendor selection 4
  • Heterogeneous vendor alignment 5
  • Multiple potential software system and hardware upgrades 4
  • Reliance on Subject Matter Experts (SMEs) 4
  • Managing Disruptive Emerging technologies (e.g., mobile apps, tablets) 3
  • Workflow and process re-engineering 4
  • Compliance with HIPAA and possibly the FDA 3
  • Individual State laws regarding patient privacy that go beyond HIPAA requirements and constraints 3
  • Testing, Verification and Validation 3
  • Documentation 2
  • Training 2
  • Et cetera?

(more…)