Uma plataforma aberta, orientada ao domínio, para o desenvolvimento de sistemas de e-saúde flexíveis
Sobre Este Site | Wiki | Jira | CKM

Agências Governamentais

Three key problems need to be solved for government e-health programmes:

  • the sharing of health information across provider enterprises, enabling healthcare professionals to deliver efficient team-based care;
  • the sharing of health information between systems where it is captured and consumer systems, e.g. decision support, medication management;
  • the computability of health information, ensuring that the power of ICT can be used safely on data, e.g. in support of medical research.

If these requirements can be met, the quality of preventative medicine, medical research, and medication management, to name a few, should significantly increase. Similarly the efficiency of data collection (capture once, share many times) should reduce the costs and adverse events in the system. The key to solving these problems is 'standardisation', but not just any standardisation. Firstly, not only does the data representation have to be standardised so as to be shared, its semantics - i.e. clinical structure and meaning - have to be standardised. A standard approach to querying is also needed.

openEHR supports such an information infrastructure, because it is designed to represent semantic models of content, from the GUI through to the database. It is an integrated framework rather than a set of disparate official standards which themselves need to be integrated. It supports the definition of clinical content via archetypes - in fact, the archetype formalism is now a CEN standard (EN13606-2), and will be an ISO standard by end 2008. Via the use of openEHR Templates, shareable data sets can be defined across any jurisdiction. These features provide a basis for defining the shared clinical, demographic and administrative semantics across jurisdictions up to and including the national level.

openEHR Ecosystem - Government Bodies

What can openEHR do for you

Strategically, openEHR offers 3 key features for national e-health programmes:

  • a health computing platform approach, which opens up health data for use by multiple applications; this leads to a platform-based health ICT economy, in which various suppliers can produce back- or front-end systems that integrate across a defined interface, rather than the current situation of numerous silos;
  • clinical content and process modelling is managed by clinicians, separately from the software, using the powerful openEHR archetype and template formalisms;
  • integration of existing standards and systems currently supporting existing standards is managed semantically, using the openEHR template data schema approach.

The openEHR platform is designed to provide a coherent basis for using and integrating de jure and industry standards, including IHTSDO SNOMED CT, WHO ICD and many other terminologies, IHE services, HL7 message, document and service definitions, CEN TC251 and ISO TC 215 health standards, health standards from OMG HDTF, and many others.

How you can get involved

You can become openEHR Partner through the Organisational membership, or members of your team can become part of openEHR as the Individual members. Find out more about membership.

How openEHR works for others

The clinical modelling is already in use at the UK NHS, where some 220 archetypes and 45 templates have been developed in 2007/2008 (NHS archetypes; NHS templates), and is under review by many other government e-health programmes, including in Australia, Denmark, Brazil and various Eastern European countries. In 2008, the Danish and Swedish governments decided to use openEHR for clinical modelling.

For list of countries which are using openEHR technology see who is using openEHR.



Agradecimentos: Atlassian (Jira, Confluence) | NoMagic (MagicDraw UML) | AsciiDoctor (publishing) | GitHub (DVCS) | LAMP dev community