The First Polish Nationwide Implementation Guide for HL7 CDA

Slides:



Advertisements
Similar presentations
HelsIT 2010 Alberto Sáez Torres Sacyl Interoperability Office Junta de Castilla y León Experience of ePrescription in Spain using HL7 V3 September 21 th,
Advertisements

E-health Initiatives in Poland
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session esMD Requirements, Priorities and Potential Workgroups – 2:00pm.
Centers for Medicare/Medicaid (CMS) Clinical Trials Policy (CTP) Training January 2009, Slide 1 Background: In 2000, Medicare issued a National Coverage.
The Treasure Hunt—Keys to Unlocking Radiology Reimbursement PAYMENT Walt Blackham, MS, RCC Radiology Business Management Association, RBMA.
A Primer on Healthcare Information Exchange John D. Halamka MD CIO, Harvard Medical School and Beth Israel Deaconess Medical Center.
Part II Objectives F Describe how policies and procedures are used F Identify different types of P & P F Describe the purpose and components of a Policy.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
EsMD Background Phase I of esMD was implemented in September of It enabled Providers to send Medical Documentation electronically Review Contractor.
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session Charter Discussion – 9:30am – 10:00am October 18, 2011.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
Pharmacy and Therapeutics Committee
E-Referral enabled collaborative health care Opportunities and considerations Presented by: Sasha Bojicic Emerging Technology Group Canada Health Infoway.
1 Public Outreach October 2008 By Adelina Murtezaj – Public Relation Officer For Inaugural Partnership Activity between ICC and ERO.
18th Symposium of the Central and East European Chambers of Physicians Professional self-government of physicians in Poland national report Konstanty Radziwill.
IHE Radiology –2007What IHE Delivers 1 Christoph Dickmann IHE Technical Committee March 2007 Cross Domain Review PCC.
E-Health – Pan UK ? HL7 UK 2006 Dr. Paul Woolman Clinical Information Standards Manager NHS Scotland.
Sharing Value Sets (SVS Profile) Ana Estelrich GIP-DMP.
Medical Law and Ethics, Third Edition Bonnie F. Fremgen Copyright ©2009 by Pearson Education, Inc. Upper Saddle River, New Jersey All rights reserved.
+ National and Institutional Guidelines on Conflict of Interest in Physician-Industry Relationships.
1 E-Health Source: Information Systems for Healthcare Management, 6th Edition Authors: Charles J. Austin and Stuart B. Boxerman Health Administration Press.
© 2013 The McGraw-Hill Companies, Inc. All rights reserved. Ch 8 Privacy Law and HIPAA.
Research Services Research Services Presentation to Department of Paediatrics Gill Rowe Head, Research Services, Medical Sciences 23 September 2015.
Standardization Roadmap in EE Janek Metsallik Chief Architect Estonian eHealth Foundation.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
Medication Error Reduction Principles in Practice Copyright © – Academy of Managed Care Pharmacy (AMCP)Slide 1.
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development 1.
IMPLEMENTATION OF ACTION PLAN FOR SUMMARY CPV REGULATION & IMPLEMENTATION Using of CPV codes became mandatory in Europe from December 16, 2003.
Component 11/Unit 2a Meaningful Use of the Electronic Health Record (EHR)
DICOM SR / CDA Rel.2 Mapping San Antonio WGM, May 2006 Helmut König Co-Chair II SIG / DICOM WG20 Siemens Medical Solutions.
West Virginia Information Technology Summit November 4, 2009.
Seniors’ Health Program Kevin Ring, Human Resources.
Chapter 7: Indexes, Registers, and Health Data Collection
1 IHE ITI White Paper on Authorization Rough Cut Implementation Opportunities for BPPC Dr. Jörg Caumanns, Raik Kuhlisch, Olaf Rode Berlin,
Medical law and its place in the system of law and legislation in Ukraine. Legislative provision in healthcare in Ukraine.  The concept, object, method.
September, 2005What IHE Delivers 1 Presenters Scanned Documents.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
Agenda What is the My Health Record System? What information is in My Health Record? Organisational Requirements and Identifiers Accessing the My Health.
Week 12. Lecture 2. Health Law & the EU Cross-border healthcare: patients’ rights.
Lithuania eHealth Overview Normantas Ducinskas Head of eHealth Coordination and Implementation Division Lithuania MoH.
EHealth Development Vision. eHealth ojectives Healthcare systems and network focused on the patient: Not patient runs between institutions but the patients’
 Pharmaceutical Care is a patient-centered, outcomes oriented pharmacy practice that requires the pharmacist to work in concert with the patient and.
HIPAA Training. What information is considered PHI (Protected Health Information)  Dates- Birthdays, Dates of Admission and Discharge, Date of Death.
Ministry of Labour, Health and Social Affairs of Georgia Development of e-Health system in Georgia.
V April 2016 Training Guide 1 NOTE: All screen shots from Communicare indicate PCEHR. Any reference to the PCEHR or the My Health Record within this.
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill/Irwin Chapter 2 Clinical Information Standards – Unit 3 seminar Electronic.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
ABC-MAP Act 191 of 2014 September 16, 2016 Pennsylvania’s Prescription Drug Monitoring Program (PA PDMP)
Modified Stage 2 Meaningful Use: Objective #8 – Patient Electronic Access Massachusetts Medicaid EHR Incentive Payment Program July 19, 2016 Today’s presenter:
The Czech Health System – its Presence and Future
Managed Care Models: The Benefit vs. Cost Balance
eHealth Standards and Profiles in Action for Europe and Beyond
Modified Stage 2 Meaningful Use: Objective #9 – Secure Electronic Messaging Massachusetts Medicaid EHR Incentive Payment Program July 19, 2016 Today’s.
Development of national eHealth system
Eligibility and evaluation
Modified Stage 2 Meaningful Use: Objective #2 – Clinical Decision Support Massachusetts Medicaid EHR Incentive Payment Program July 7, 2016 Today’s presenter:
US Prescribers and Biosimilars Naming
Unit 5 Systems Integration and Interoperability
Ministry of Health Montenegro ERASMUS+ KA2 PROJECT:
Batch Prescribing Repeat Dispensing
Introduction to Health Insurance
Health Information Exchange Interoperability
1115 Demonstration Waiver Extension Summary
Modified Stage 2 Meaningful Use: Objective #10 – Public Health Reporting Massachusetts Medicaid EHR Incentive Payment Program July 21, 2016 Today’s presenter:
How Do I Evaluate Workflow?
Overview of CRISP Connectivity Process
4. Allergy severity The severity of an allergy is not displayed by the CDA Display Tool, and this is considered relevant to the HP. PT MAJOR The severity.
Titan SenQuest Benefit Plans
Health Information Exchange for Eligible Clinicians 2019
Part II Objectives Describe how policies and procedures are used
Presentation transcript:

The First Polish Nationwide Implementation Guide for HL7 CDA Roman Radomski, iEHR.eu 22 Nov 2013, London

eHealth in Poland The main project of Polish eHealth aims at building the central information system supporting common exchange of electronic medical documents. Three types of documents: eReferral, ePrescription and eOrder of Supply are to be uploaded to the central repository to be accessed by the potential service providers. Other documents are to be stored locally, but their metadata will be sent to the same central system and published in the form of document registry.

HL7 v3 Implementation Guide HL7 CDA and V3 have been chosen as the standards for documents and messages to be exchanged with the central system. Due to the official project timeline, the large scale amendments of the current regulations and printed document forms were excluded. Draft CDA implementation guide for all 3 document types has been developed by iEHR.eu and distributed by the official government agency CSIOZ for review. The message template for other documents metadata exchange has been designed on the basis of the HL7 Medical Records R-MIM.

The overall model of IG artifacts

Templates defined in IG

Local extensions Most of the clinical concepts represented in the documents have been successfully mapped to the CDA, although 8 local extensions had to be defined. One extension has been defined for the HL7 v3 message being sent to the central repository.

Entitlement document The clinical document may contain information on non-clinical document allowing patient’s entitlement to the particular medical service coverage plan. The information consists of the document type and the document number (identifier). The special entitlement resulting from the document is not explicit in the document. The entitlement is subject to the operational context (planned service, local conditions, region) and may vary in time, but it does not change the document information.

Entitlement document id.root = OID nodes for entitlement documents identifiers code.codeSystem = OID node for entitlement documents types value set Constraint: Document id and code

Special entitlement There are special entitlements (e.g to the drug refund coverage plans) that should be indicated in the prescription document. The dictionary of those coverage plans is regulated by law.

Special entitlement code.code = "PUBLICPOL" code.codeSystem = "2.16.840.1.113883.11.19350” (ActInsurancePolicyCode) code.qualifier.name.code = "RLEKUD" (drug refund based on special entitlement) code.qualifier.name.codeSystem = OID node for coverage plans value set code.qualifier.value.codeSystem = OID node for special entitlements value set Constraint: CoveragePlan.code

Coverage eligibility confirmation There is a procedure for online confirmation of patient eligibility to the national health insurance. The confirmation has a form of a string and needs to be included in the clinical document issued when refunded service is performed. The confimation string is not an identifier of an insurance policy or any other entitlement document.

Coverage eligibility confirmation id.root= OID node for coverage eligibility confirmation identifiers code.code = "ELG " (eligible) code.codeSystem = "2.16.840.1.113883.11.17488" (ActCoverageEligibilityConfirmationCode) Constraint: CoverageEligibilityConfirmation id and code

Multiple birth indicator and order number Newborns are identified by their mother identifier and the birth date. Multiple birth newborns are identified by their mother identifier, the birth date and the birth order number. All those identifying data needs to be included in every clinical document until the proper national identifier is given - usually it takes couple of weeks.

Multiple birth indicator and order number

Close person There are specific document forms in Poland which require providing given names of patient’s parents as an additional patient identifying information. This is not an information about patient’s guardian. This is not a participation in the act of clinical document or in any act being documented. The document does not contain any other information about patient’s parents.

Close person code.codeSystem = "2.16.840.1.113883.11.19563" (PersonalRelationshipRoleType) Constraint: PersonalRelationship.code

Physician speciality Prescriptions for specific drugs and medical equipment supply require to be issued by physicians of particular specialities. Common practice is to include all medical specialities of document authenticator in every clinical document issued. The document content and context may not be relevant to the physician’s medical speciality. The dictionary of medical specialities is regulated by law.

Physician speciality code.codeSystem = OID node for physician specialities value set Constraint: Qualification.code

Drug payment level Drug may be refunded on various levels according to the public insurance/coverage plan. The same drug may be refunded on different levels depending on clinical context. Physician is expected to determine the patient’s payment level for the drug being prescribed. The dictionary of drug payment levels is regulated by law. The national health fund conducts continous fraud detection to ensure proper drug refund processes.

Drug payment level code.code = "PUBLICPOL" code.codeSystem = "2.16.840.1.113883.11.19350” (ActInsurancePolicyCode) code.qualifier.name.code = "POLEKR" (refunded drugs payment levels) code.qualifier.name.codeSystem = OID node for coverage plans value set code.qualifier.value.codeSystem = OID node for refunded drugs payment levels value set Constraint: CoveragePlan.code

Drug substitution The default rule is that pharmacist can substitute the prescribed drug with its equivalent, unless the drug prescription contains „no substitution” remark. The problem of drug substitution is rather sensitive, due to business competition between pharmaceutical companies and its potential influence on the medical professionals.

Drug substitution code.code = "N" (none) code.codeSystem = "2.16.840.1.113883.11.16621" (ActSubstanceAdminSubstitutionCode) Constraint: Substitution.code

Supporting Clinical Statement The message containing metadata of clinical document being issued is sent to the central repository. This message has to contain information about diagnosis placed in the context of the document.

Supporting Clinical Statement Medical Records Clinical Statement code.codeSystem = OID node for official Polish translation of ICD-10 Constraint: Observation.code

New Timeline for the Polish eHealth Agenda The central system (P1) to be ready by mid 2014 First production use of P1 at beginning of 2015 The electronic drug prescription obligatory for all healthcare providers in 2015 or 2016 Other documents will be obligatory gradually from 2016