Ekagra caDSR Forms Interchange Feasibility of using ODM & CDA Nov 13, 2008 Ashwin Mathur

Ekagra Background

Ekagra The need To be able to represent Forms templates in a consistent ‘standards’ based format for sharing with other systems

Ekagra Forms Domain Model

Ekagra Requirements Information to be captured - Form metadata Questions Question Text CDE IDs Header info Long Name, Definition, Context, etc. Form Structure Modules Name Order Form Behavior Skip Patterns (if any)

Ekagra Clinical Document Architecture (CDA) HL7 standard for exchanging clinical documents For transmission of actual clinical data Uses HL7 v3.0 complex datatypes Levels of compliance (Level 1, Level2, Level3) in increasing order of conformity

Ekagra CDA Header

Ekagra CDA body mappings

Ekagra CDA Example Link

Ekagra Requirements  Information to be captured – CDA approach  Forms meta-data ◦ Questions  Question Text  CDE IDs ◦ Header info  Long Name, Definition, Context, etc.  Forms structure ◦ Modules  Name  Order  Forms Behavior  Skip Patterns (if any)  Additional CDA requirements ◦ Header fields data (recordTarget, author, etc.) ◦ Responses to each question ◦ Code system mappings to each response X X X X X

Ekagra CDA Summary Advantages Strongly typed Different levels of conformity Human-readable & machine computable (for Level 3 conformant documents) Disadvantages (Forms Perspective)  Needs actual data for compliance  Header elements like recordTarget, author & custodian are mandatory  Elements cannot be referenced - no re-use  No support for data validation  No explicit ordering of sections  No support for skip-patterns

Ekagra Operational Data Model (ODM) CDISC Standard for ‘interchange and archive of clinical trials data’ Includes clinical data along with its associated metadata, administrative data & reference data

Ekagra ODM Mappings

Ekagra ODM Meta-data Mappings

Ekagra ODM Example Link

Ekagra Requirements  Information to be captured – ODM approach  Forms meta-data ◦ Questions  Question Text  CDE IDs ◦ Header info  Long Name, Definition, Context, etc.  Forms structure ◦ Modules  Name  Order  Forms Behavior  Skip Patterns (if any)

Ekagra ODM Summary Advantages Elements loosely coupled – promotes re-use Supports data validation Supports skip-patterns Supports module & question ordering Supports data and metadata in one document Disadvantages Not strongly typed Not easily human- readable

Ekagra ODM for CDA Clinical Global Improvement Patient is suicide risk? Patient in remission 1)Record Target details 1)Patient information 1)Patient Name ______ 2)Patient Address 1)Home Number ______ 2)City ______ 3)State ______ 4)Country ______ 5)Zip ______ 2)Author details 1)Author Name ______ 2)Author Address 1)Home Number ______ 2)City ______ 3)State ______ 4)Country ______ 5)Zip ______ 3)Custodian details 1)Custodian Name ______ 2)Custodian Address 1)Home Number ______ 2)City ______ 3)State ______ 4)Country ______ 5)Zip ______ 4)Patient Health Info 1)Clinical Global Improvement )Patient is suicide risk? Yes No 3)Patient in remission Yes No C D A

Ekagra The proposed approach Use ODM to capture form meta-data form data CDA meta-data CDA data Produce CDA from captured data ODM Container CDA Form Data CDA Data Form Metadata CDA Metadata

Ekagra Issues 1. Datatypes - CDA has complex HL7 datatypes while ODM has simple datatypes Workaround: The CDA complex datatypes can be broken down into multiple parts with simple datatypes in a ODM element Further restrictions on the data can be applied using the ‘RangeCheck’ element in ODM

Ekagra Example Clinical Global Improvement Patient’s suicide risk Patient in remission House Number City State PatientName Author Name What is the Clinical Global Improvement Patient’s suicide risk Patient in remission C D AO D M Form > xslt C D A John Doe 21 North Ave Burlington MA USA 21 North Ave Burlington MA USA SELF Good Health Clinic 21 North Ave Burlington MA USA Clinical Global Improvement 2 > Patient is suicide risk? Yes Patient in remission Yes

Ekagra ODM-CDA Requirements  Forms requirements  Forms meta-data ◦ Questions  Question Text  CDE IDs ◦ Header info  Long Name, Definition, Context, etc.  Forms structure ◦ Modules  Name  Order  Forms Behavior  Skip Patterns (if any)  Additional CDA requirements ◦ Header fields data (recordTarget, author, etc.) ◦ Answers to each question ◦ Code system mappings to each answer (for enumerated value domains)

Ekagra Summary CDAODM Forms meta-data Questions Question Text CDE IDs Header infoLong Name, Definition, Context, etc. Forms structure Modules Name Order Forms Behavior Skip Patterns (if any) CDA requirements Header fields data (recordTarget, author, etc.) Answers to each question Code system mappings to each answer X X X X X

Ekagra Conclusion CDA is instance-specific and needs actual data to be generated ODM provides good support for capturing meta-data and data Data needed to generate CDA can be captured in an ODM ODM -> xslt -> CDA

Ekagra Questions?