MEDIQ EuroRec Seal Preparing a certification session Morten Bruun-Rasmussen √ Vilnius, Lithuania. 26 th January, 2012.

Slides:



Advertisements
Similar presentations
2 Slovenia Signed Contract of Confidence for the period Compliance assessment for one programme for the new period Experience of a Certifying.
Advertisements

SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Quality Manual for Interoperability Testing
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Milan Zoric, ETSI.
Testing and Quality Assurance
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
Software Quality Assurance Plan
1 Software Engineering Lecture 11 Software Testing.
Corrective & Preventive Action Programme l Corrective and preventive action managed by one programme l Closely linked to the internal audit programme l.
Component 4: Introduction to Information and Computer Science Unit 9: Components and Development of Large Scale Systems Lecture 5 This material was developed.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 12: Managing and Implementing Backups and Disaster Recovery.
Chapter 7 Database Auditing Models
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Jos Devlies, Eurorec.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Software Testing Prasad G.
Network security policy: best practices
Instructions and forms
Chapter 7 Database Auditing Models
Washington Metropolitan Area Transit Authority Pre-Proposal Conference Sourcing and Contracts Management System (CMS) Solution Request for Proposal FQ
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
CS 4310: Software Engineering
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
SQA Architecture Software Quality By: MSMZ.
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
GEORGIA ELECTRONIC CONVICTION PROCESSING SYSTEM 1 Georgia Electronic Conviction Processing System (GECPS)
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
FDA Regulatory review in Minutes: What Product Development Executives Need-to-Know. Specifically, frequent causes of recalls and related areas that investigators.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
Purchasing Director’s Meeting MFMP 2.0 Upgrade Status February 15, 2007.
Software Configuration Management (SCM)
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 12: Managing and Implementing Backups and Disaster Recovery.
Mass Mail Out & VR Cards. Mass Mail Out of Voter Registration Certificates Certificates must list jurisdictional numbers for seven (7) designated territorial.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
MEDIQ EuroRec’s First Draft List of EHR Certification Criteria Knut Bernstein MEDIQ
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 7 Database Auditing Models.
© Mahindra Satyam 2009 Configuration Management QMS Training.
ISO 9001 – an overview Tor Stålhane IDI / NTNU. ISO 9001 and software development ISO 9001 is a general standard – equally applicable to software development.
EHR Systems Quality Labelling and Certification Danish Case Morten BRUUN-RASMUSSEN MEDIQ Belgrade. 22 nd November, 2011.
1 Chapter Nine Conducting the IT Audit Lecture Outline Audit Standards IT Audit Life Cycle Four Main Types of IT Audits Using COBIT to Perform an Audit.
Green Partnerships Kick-off meeting Expenditure reporting procedure in PRESAGE- CTE JTS MED Programme cofinancé par le Fonds Européen de Développement.
ESA ODFCB # 4 Peter Granseuer1 ESA ODFCB Charter Peter Granseuer MSM-EOI
Software Quality Assurance and Testing Fazal Rehman Shamil.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
1 test10b Software Testing Necessary to measure and certify quality in software.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Research Documentation Betty Wilson, CIP, MS Senior Compliance Manager MU IRB Lori Wilcox, EdD Director of Academic Compliance, Corporate Compliance.
Slide 1 POA Seminar 02 March 2016 Personnel Competence Including Certifying Staff and Release to Service Andy Swift / Michael Greer.
0 Design Change Construction & Completion Management (Outline and related procedures) Hanul NPP Engineering Center.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Testing.
Testing Tutorial 7.
Introducing ICA-Requirements Module 3: Functional Requirements for Records in Business Systems
Software Testing.
Software Testing.
Auditing Information Technology
Controlling Computer-Based Information Systems, Part II
Session II: System authority for ERTMS 4RP Trackside approval
IS442 Information Systems Engineering
Lecture 09:Software Testing
Fundamental Test Process
15 years experience with Quality Labelling and Certification
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
LESSON 01 Hands-on Training Execution
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Presentation transcript:

MEDIQ EuroRec Seal Preparing a certification session Morten Bruun-Rasmussen √ Vilnius, Lithuania. 26 th January, 2012

Guideline for running a test  Introduce a uniform and transparent methodology for the certification of Electronic Health Record systems in Denmark (and Europe)  It is mandatory to follow the guideline by the certification of a system: Result and documentation of specific certifications can be compared Can be repeated – with the same results – by more authorised certifiers MEDIQ

Compliance and conformance  The certification, documents to what extend the software product is compliant with the conformance criteria being tested  The certification, does not ensure: Stress testing: system performs with expected volumes Execution testing: system achieves desired level of proficiency Recovery testing: system can be returned to an operational status after a failure Operations testing: system can be executed in a normal operational status Security testing: system is protected in accordance with importance to organisation MEDIQ

Certification methodology EHR system EuroRec Seal Guideline Procedure Certification documents Delivery document. # of tests performed Approved Not approved Self evaluation Test-log Validation Test-log Test data set Test criteria

EuroRec Seal Statements MEDIQ

Test scenarios  The objective is to test and ensure that the business process flows are tested from end to end  Scenarios are simple and based on a number of steps, where each step gives precise instruction on what to do  In average a test of a EuroRec Seal statement will include 3-4 steps. MEDIQ

Test data  Data which have been specifically identified for use by testing the EHR against the EuroRec Seal  Some data may be used in a confirmatory way, typically to verify that a given set of input to a given function produces some expected result  It is mandatory to use the specified test data in the scenarios, unless it is clearly stated the test data only serve as examples MEDIQ

Conformance criteria  The aim is to test and gain confidence in the correct functioning of the implementation with respect to a specific EuroRec statement  Based on a functional testing (black- box testing) with the emphasis on testing the externally observed functionality against the EuroRec Seal. MEDIQ

EuroRec Seal #1,GS MEDIQ Each version of a health item has a date and time of registration. Quoted Statement 1.Search for patient 2.Add a health item, eq. a diagnose 3.Add a health item, eq. an intervention 4.Add a health item, eq. a consultation note Test scenario 1.Patient #1 2.Diagnose: Chronic Heart Failure 3.Intervention: Electrocardiogram 4.Consultation note: Congestive heart failure with severe LV systolic dysfunction Test data Check that the date and time for the diagnose, the intervention and the consultation note are the same as the date and time for the registration. The registration is the date and time, when the decision or process happened (not always the date and time for entering the data). Criteria

EuroRec Seal #4: GS Each version of a health item has a status of activity, e.g. active or current, inactive, history or past, completed, discontinued, archived. Quoted Statement 1.Search for patient 2.Search for a health item, eq. diagnose, intervention or consultation note 3.Display the current status of activity 4.Update the status of activity 5.Repeat step 2-4 minimum 3 times and update status of activity Test scenario 1.Patient #1 2.Diagnose: Chronic Heart Failure 3.N/A 4.Status of activity: State 1, state 2, state 3… 5.N/A Test data Check that the status of activity for a health item (eq. diagnose, intervention, consultation note) can have different status of activity. Conformance criteria

Test environment  The vendor will provide minimum two networked computers with printers etc. All necessary components and resources for running the test shall be available (PCs, laptops, printers, servers etc.)  The system shall be preloaded with necessary test data before the test Number of patients and data descriptions are specified in the guideline  The EHR system shall be configured as a “live” system running in daily operation MEDIQ

Start Vendor Self-evaluation Week 1Week 2Week 3Week 4Week 5 Valida tion Week 6 Vendor fix errors if not approved Valida tion Test log Test log Delivery document Test log Delivery document

Test log  A template which is used to document the actions and results of the test of the EHR system against the EuroRec Seal  It is mandatory to use the test log at both phase I – self evaluation and phase II – validation  If an error during the test is detected it shall be documented exhaustive MEDIQ

Delivery document  The objective is to document if the EHR system has passed or not passed the test.  After the end of phase II – validation, the certifier will fill out a delivery document  The delivery document is to be signed by the representative from the vendor and the representative from the certification organization. MEDIQ

EuroRec certificate MEDIQ  CSC announces the achievement of the EuroRec certificate world- wide

Thank you MEDIQ