CCDA for Business Intelligence

Presenting the CCDA "IZA" Architecture

Transcript

1.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 1 CCDA  “Iza”  Architecture   Ron  Sweeney,  Integra/on  Required   November  2,  2013  
2.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 2 Purpose   Possible  Use  Cases   Meaningful  Use  and  Healthcare  Interchange  advancements  have   driven  the  use  of  Consolidated  Clinical  Documents  to  help  care   givers  digest  significant  amounts  of  clinical  informa/on  about   pa/ents  quickly  and  within  the  means  of  human  consump/on.   These  documents  can  be  appropriated  programma/cally,  and   then  digested  to  enumerate  characteris/cs  about  a  pa/ent  that   can  be  used  for  business  intelligence  or  user  context  switching   for  known  characteris/cs.                
3.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 3 CCDA?   Consolidated  Clinical  Document  Architecture   CCDA           CCDA           CCDA           XML  (MACHINE  READABLE)       HTML/PDF(HUMAN  READABLE)       “CARFAX  for  HUMANS”       A  CCDA  is  a  standard  document  architecture  in  healthcare  that  projects   pa/ent  informa/on  in  a  portable  and  importable  format  for   interchange  throughout  the  care  of  the  pa/ent  amongst  phr  and  emr   so[ware.            
4.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 4 IZA?   Based  on  a  CCDA  Document  this  pa8ent  IS  A…   A  method  of  determina/on  of  a  defined  pa/ent  profile.       Example:  Pa/ent  IS  A  Smoker,  because  the  CCDA  Social  History   smoking  cessa/on  proper/es  exist.               Smoker   Person   .Iza?  =   CCDA   The  fixtures  that  determine  the  profile  from  the  CCDA  are  “Izms.”                 +  
5.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 5 IZM?   A  Business  Driven  Method  that  Enumerates  the  “IZA”   If  we  have  a  couple  objects  (Pa/ent  and  CCDA),  we  can  write   methods  or  dic/onaries  that  use  these  object  proper/es,  coined   “izms.”         These  are  codified  values   that  are  resident  in  a  CCDA   Social  History  Sec/on,  each   of  them  meaning  something   as  indicated  in  the  izm.       The  izm  says,  hey  if  you  are   any  of  these  codes,  you  are  a   smoker.      
6.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 6 The  Point   Possible  Use  Cases   Anywhere  in  the  ePa/ent  or  eMember  experience,  at  logon,  or   elsewhere,  provide  a  different  experience,  capability,  naviga/on,  or   exposure  to  relevant  services  for  the  enumerated  profile  through  the   Iza  architecture.       Go  Download     No  Smoking  App     Go  Download     Free  CigareHe  App    
7.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 7 Example  Code   ccda-­‐iza,  a  Ruby  Gem   git clone https://github.com/sween/ccda-iza.git !          
8.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 8 Demo   Example  App   “Given  an  authen/cated  ePa/ent  and  associated  CCDA  (CCD  HITSP/ 32),  enumerate  whether  or  not  the  ePa/ent  is  a  smoker,  if  the   ePa/ent  is  a  smoker,  deny  them  insurance.    If  they  are  not  a   smoker,  abempt  to  sell  them  cigarebes.”              
9.   Ron  Sweeney,  Integra/on  Required,  LLC         CONFIDENTIAL: Integration Required, LLC 9 Concluded   Ron  Sweeney,  Integra/on  Required   March  2,  2013