2015
DOI: 10.1016/j.ijmedinf.2015.05.016
|View full text |Cite
|
Sign up to set email alerts
|

Archetype-based data warehouse environment to enable the reuse of electronic health record data

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
28
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 42 publications
(29 citation statements)
references
References 27 publications
0
28
0
Order By: Relevance
“…This critical barrier only occurred in the literature once for the U.S., and only recently [ 27 ]. Several other articles were identified worldwide on the subject [ 28 – 30 ]. Providers have voiced their discontent with the lack of interoperability established by government agencies, which enables the static nature of EHR development at the vendor [ 27 ].…”
Section: Discussionmentioning
confidence: 99%
“…This critical barrier only occurred in the literature once for the U.S., and only recently [ 27 ]. Several other articles were identified worldwide on the subject [ 28 – 30 ]. Providers have voiced their discontent with the lack of interoperability established by government agencies, which enables the static nature of EHR development at the vendor [ 27 ].…”
Section: Discussionmentioning
confidence: 99%
“…Thus, it is possible to support cohort selection of appropriate study patients across various sites and to collect patient informed consent only in a second step for the finally selected patients. Another technically interesting approach from the Scandinavian countries relies on the use of openEHR to extract data from several source EHRs [110]. It has long been recognized that data transfer between different EHR systems relies on both syntactic and semantic constraints (Fig 2) [ 111,112].…”
Section: Data Integration Interoperability and Systems Federationmentioning
confidence: 99%
“…Our EHRS approach consists of the same XML database architecture, comparable to another archetype-based data warehouse environment [22]. Because we want to build up the EHRS on W3C standards, we extended the REST architecture using the W3C XForm method for a binding of EHR elements to web form items, like already done in the Single Source Architecture of x4T [23,24] for CDISC ODM.…”
Section: Archetype-based Ehr-development Frameworkmentioning
confidence: 99%