Electronic Health Recordsand Electronic Case Records in 2012


Published on

Doug Neilson

Published in: Health & Medicine, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Electronic Health Recordsand Electronic Case Records in 2012

  1. 1. Electronic Health Records and Electronic Case Records in 2012 It’s not as hard as we think!
  2. 2. Agenda <ul><li>The problem we’re trying to solve </li></ul><ul><li>Examples of EHR and ECR in 2012: </li></ul><ul><ul><li>Patient care in a primary care setting </li></ul></ul><ul><ul><li>Provision of long term care </li></ul></ul><ul><ul><li>Medical incident from an Ambulance Services perspective </li></ul></ul><ul><ul><li>Patient care in a secondary care setting </li></ul></ul><ul><li>Information Architecture </li></ul><ul><li>Making it happen . . . </li></ul>
  3. 3. The problem we’re trying to solve <ul><li>Quality information is necessary to deliver the optimum health service but the information required is often held elsewhere (and is not immediately available) and : </li></ul><ul><ul><li>Patients worry about misuse of their health information and that the data is unsafe </li></ul></ul><ul><ul><li>If data was provided, there is a concern that practitioners would get more information than they need and there are particular concerns regarding access to mental health and sexual health data </li></ul></ul><ul><ul><li>Some concerns that releasing information would result in less control of patient management and/or increased scrutiny of clinical decisions etc . </li></ul></ul><ul><li>Therefore, discussion about EHRs and ECRs tends to stop at the “patient privacy barrier” and progress has been minimal </li></ul><ul><li>This paper describes what an EHR/ECR capability might look like if these concerns were addressed </li></ul>
  4. 4. Scenario 1 – Primary Care <ul><li>Practice Management System and online notifications of external health events operate side by side at the GP/Nurse’s desktop </li></ul><ul><li>Data displayed from multiple sources as one virtual record (bloods, medications etc.) </li></ul><ul><li>Identifies other health providers involved in a patient’s care </li></ul><ul><li>Electronic Support for Clinical Decisions </li></ul><ul><li>Moderated online access by patients to their data </li></ul>
  5. 5. Scenario 2 – Long Term Care <ul><li>Specialists can access key data from PMS – medications, allergies etc. </li></ul><ul><li>All providers involved see the same (appropriate) data to ensure continuity of care </li></ul><ul><li>Management of tests and reviews (scheduling and reporting) </li></ul><ul><li>Electronic Case Records provide a vertical slice of data – ad hoc enquiry for other information </li></ul>
  6. 6. Scenario 3 – Ambulance Services <ul><li>“ Break glass” access to critical patient data where patient consent is not possible </li></ul><ul><li>Observations and baselines etc. automatically transmitted to the hospital </li></ul>
  7. 7. Scenario 4 – Secondary Care <ul><li>Access to all patient history (sexual and mental health by exception) </li></ul><ul><li>Medical warnings and alerts, pharmaceutical use and laboratory test results </li></ul><ul><li>Summary by default – drill down to detail where required </li></ul><ul><li>Contact information provided if more clinical detail needed </li></ul>
  8. 8. Information Architecture Point of Care Health Event Summaries Health Event Records Clinical Record – Patient B Health Event Summaries Health Event Record = “ minimum (clinical) data set” for that type of event Health Event Summary = transactional record of event Health Event Records Clinical Record – Patient A
  9. 9. The Heath Event Summary Index Record Identifier Unique Serial Number Definition Event type, security indicator Patient Identity NHI, public interest flag Health Worker Identity HPI (Worker, Organisation and Facility) Date/Time Inputs (repeating) Serial number of records created in the same transaction Outputs (repeating) Serial number of services or interactions that resulted from this transaction Audit (repeating) HPI (Worker) and date/time of access
  10. 10. Information Architecture District, Community and National Repositories Connected Health Networks DHB Health Event Summary Index Health Event Records PHO
  11. 11. Information Architecture National Collections etc Ad hoc report Communicable Disease Register Rheumatic Fever Register Cancer Register National Immunisation Register Integrated Diabetes Management DHB .. Health Event Summary Index Integrated Cardio Vascular Disease Management Report Specification DHB 2 DHB 1 DHB n Data Extract(s)
  12. 12. Information Architecture Point of Care Enquiry DHB .. Health Event Summary Index DHB 2 DHB 1 DHB n Data Extract(s) User HES1 HES2 HER1 HES3 HER2 Connected Health Networks
  13. 13. Making it happen . . . <ul><li>Technology is not a barrier </li></ul><ul><li>Health Information Strategy for NZ sets the direction </li></ul><ul><li>Work already underway including: </li></ul><ul><ul><li>Authentication and security </li></ul></ul><ul><ul><li>Connected Health Networks </li></ul></ul><ul><ul><li>Online Forms Server </li></ul></ul><ul><ul><li>Common data dictionary </li></ul></ul><ul><ul><li>Code sets and data standards </li></ul></ul><ul><li>Still work to be done in the policy, legislation and regulation space </li></ul>
  14. 14. Thank you for listening <ul><li>I’m keen to continue the discussion. You can contact me at: </li></ul><ul><ul><li>Doug Neilson </li></ul></ul><ul><ul><li>Information Strategist </li></ul></ul><ul><ul><li>PO Box 12 698 </li></ul></ul><ul><ul><li>Thorndon </li></ul></ul><ul><ul><li>Wellington 6144 </li></ul></ul><ul><ul><li>Phone 027 446 7224 </li></ul></ul><ul><ul><li>eMail [email_address] </li></ul></ul>