CCDAs from Soarian – Vital Signs component w/o discrete data

[Peter Heggie]

I know this is a stretch, as far as its applicability to Cloverleaf.. We do use the Cloverleaf Direct Adapter to send and receive CCDAs, and we use Cloverleaf interfaces (especially tcl) to reformat output that does not conform to the current ONC standards.

We are converting our HIS to Soarian, and Soarian Clinicals (or the application integration services component) generates the CCDA where the Vital Signs component/section does not have a discrete data entry, just a display text area. This is kind of a step backward from our current HIS, which does generate a Vital Signs section with both display and discrete data areas.

When we send CCDAs to systems which parse and consume data using software, they look for data in the discrete data area, not the display data.

Right now I’m coding TCL to read the display data and create an equivalent discrete data section on the fly.

I’m wondering A) if anyone else has Soarian Clinicals and does it’s CCDAs have a ‘full’ Vital Signs component, and B) can anyone comment on other HIS’s CCDA formatting and content as far as being able to conform to current ONC standards?

Thanks,

Peter

Peter Heggie
PeterHeggie@crouse.org

Topic