Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
The prEN13606-1 Reference Model standardizes the communication of EHR instance data,permitting EHRs to be exchanged. Due to naming and meaning attributes in the ReferenceModel these EHR_EXTRACTS will be syntactically interoperable (i.e their structure andprovenance can be understood) and semantically interpretable (i.e. the semantics is explicitand can be analyzed) but not semantically interoperable (i.e. 13606 alone does not guaranteethat different EHR systems and vendors will construct equivalent EXTRACTS, and use therecord hierarchy and terminology in consistent ways). Ensuring EHR data quality and dataconsistency are beyond its scope.The prEN13606-2 Archetype Interchange Specification standardizes the communication ofarchetypes - permitting archetypes to be exchanged between registries and EHR systems,but does not define how archetypes can be designed optimally for each clinical area, orconsistently across authoring teams.However, in order to be able to process and analyse health records inside any one systemthat originate from heterogeneous record sources, we need rich semantic interoperability. Weneed consistent and rigourous archetypes that standardise the clinical content of EHREntries, for use by clinical applications, within messages, for decision support, public healthand research.The following ingredients are still required in order for semantic interoperability to beachieved:1) an archetype ontology to map individual archetypes to a generic knowledge framework - toenable their use alongside other knowledge resources;2) Domain Base Concept Models (DBCMs), enabling sharable archetypes to be written;These models are needed to underpin the development of optimal and consistent archetypes.The openEHR Entry specialisations are well-tailored examples of this, but a variety of CENstandards (CONTSYS, HISA and GPICs) and EHR system models should be investigated foruse.3) rules about binding co-ordinated terminology values to archetype nodes
Reģistrācijas numurs (WIID)
26243
Darbības sfēra
The prEN13606-1 Reference Model standardizes the communication of EHR instance data,permitting EHRs to be exchanged. Due to naming and meaning attributes in the ReferenceModel these EHR_EXTRACTS will be syntactically interoperable (i.e their structure andprovenance can be understood) and semantically interpretable (i.e. the semantics is explicitand can be analyzed) but not semantically interoperable (i.e. 13606 alone does not guaranteethat different EHR systems and vendors will construct equivalent EXTRACTS, and use therecord hierarchy and terminology in consistent ways). Ensuring EHR data quality and dataconsistency are beyond its scope.The prEN13606-2 Archetype Interchange Specification standardizes the communication ofarchetypes - permitting archetypes to be exchanged between registries and EHR systems,but does not define how archetypes can be designed optimally for each clinical area, orconsistently across authoring teams.However, in order to be able to process and analyse health records inside any one systemthat originate from heterogeneous record sources, we need rich semantic interoperability. Weneed consistent and rigourous archetypes that standardise the clinical content of EHREntries, for use by clinical applications, within messages, for decision support, public healthand research.The following ingredients are still required in order for semantic interoperability to beachieved:1) an archetype ontology to map individual archetypes to a generic knowledge framework - toenable their use alongside other knowledge resources;2) Domain Base Concept Models (DBCMs), enabling sharable archetypes to be written;These models are needed to underpin the development of optimal and consistent archetypes.The openEHR Entry specialisations are well-tailored examples of this, but a variety of CENstandards (CONTSYS, HISA and GPICs) and EHR system models should be investigated foruse.3) rules about binding co-ordinated terminology values to archetype nodes
