Page tree
Skip to end of metadata
Go to start of metadata

Audit Framework Components Releases


VERSION

DATE RELEASED

STATUS

DOCUMENT

4.0.1

 

Wave 4 Operation Ready

(version submitted for eHMSEG adoption on )

4.0.0 RC

 

Wave 4 Release Candidate

(version to be reviewed by eHDSI Stakeholders)

2.0.0

 

Wave 3 Operation Ready

Audit Framework

1.2.1

 

Wave 2 and Wave 3 Operation Ready (hot fix)

1.2.0

Wave 2 Operation ReadyAudit Framework (1.2.0)
1.2.0

Wave 2 Operation Ready

Readiness Criteria (1.2.0)
1.1.0

Wave 1 Operation ReadyAudit Framework (1.1.0)
1.1.0

Wave 1 Operation ReadyReadiness Checklist (1.1.0)
1.0.0

Release CandidateAudit Framework (1.0.0)
1.0.0

Release Candidate. Part of Audit Framework.Audit Report (1.0.0)
1.0.0

Release Candidate. Part of Audit Framework.Readiness Checklist (1.0.0)
1.1.0

The document should be used to assess the operational readiness of the NCPeH against contractual compliance, organisational, operational, security, semantic, and technical requirements for Wave-1 countriesReadiness Criteria (1.1.0)

Introduction

Purpose


Objective and independent evidence that each NCPeH implements and operates in compliance with eHDSI Requirements, as defined by the Audit Framework.

The following eHDSI domains are considered during the eHDSI Audit process:

  1. Legal and Organisational domain
  2. Operations-Services domain
  3. Information Security domain
  4. Semantic Interoperability domain
  5. Technical Interoperability domain


Overview presentation



Audit Framework Components


Audit Framework Components

PURPOSE

Audit

Framework

The purpose of this document is to provide a complete guidance to the persons appointed to conduct audits (or assessments) on how to plan, execute, evaluate and follow-up the adherence to the Readiness Criteria as these have been set out in the eHealth Network documentation and agreements.

Readiness Criteria Checklist


The document should be used to assess the readiness of the NCPeH against the legal, organisational, operational, security, semantic, and technical requirements of its establishment and operations.


  • No labels