2022
DOI: 10.2196/36709
|View full text |Cite
|
Sign up to set email alerts
|

The Architecture of a Feasibility Query Portal for Distributed COVID-19 Fast Healthcare Interoperability Resources (FHIR) Patient Data Repositories: Design and Implementation Study

Abstract: Background An essential step in any medical research project after identifying the research question is to determine if there are sufficient patients available for a study and where to find them. Pursuing digital feasibility queries on available patient data registries has proven to be an excellent way of reusing existing real-world data sources. To support multicentric research, these feasibility queries should be designed and implemented to run across multiple sites and securely access local data… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
10
0
1

Year Published

2022
2022
2024
2024

Publication Types

Select...
7
1
1

Relationship

3
6

Authors

Journals

citations
Cited by 31 publications
(24 citation statements)
references
References 41 publications
0
10
0
1
Order By: Relevance
“…Most FHIR server implementations are optimized to handle many small, parallel requests referring to a single patient or encounter, but are slow or even return incomplete results when processing requests for bigger, cross-case/cross-patient chunks of data. A comprehensive comparison of downloading times for different FHIR server implementations is still needed though some aspects have been discussed by Gruendner et al 36 When using fhircrackr, the downloading time can be improved by (1) splitting requests in smaller chunks and sending them in parallel using the R package “parallel” and (2) by carefully choosing the most restrictive filter criterion in the first FHIR search request, when several FHIR search queries are combined. In terms of memory, the XML structure of the FHIR resources produces a lot of overhead, challenging memory capacity in large data applications.…”
Section: Discussionmentioning
confidence: 99%
“…Most FHIR server implementations are optimized to handle many small, parallel requests referring to a single patient or encounter, but are slow or even return incomplete results when processing requests for bigger, cross-case/cross-patient chunks of data. A comprehensive comparison of downloading times for different FHIR server implementations is still needed though some aspects have been discussed by Gruendner et al 36 When using fhircrackr, the downloading time can be improved by (1) splitting requests in smaller chunks and sending them in parallel using the R package “parallel” and (2) by carefully choosing the most restrictive filter criterion in the first FHIR search request, when several FHIR search queries are combined. In terms of memory, the XML structure of the FHIR resources produces a lot of overhead, challenging memory capacity in large data applications.…”
Section: Discussionmentioning
confidence: 99%
“…Für die Erhebung der Daten, die bisher noch nicht Bestandteil der elektronischen Krankenakte waren, wurden Datenerfassungssysteme (REDCap und DIS) mit standardisierten Data Dictionaries und einem vordefinierten Extraktionsprozess zur Generierung der FHIR-GECCO-Formate bereitgestellt. Für föderierte Machbarkeitsabfragen wurden diese FHIR-Server über zentral entwickelte Komponenten und sichere Datenverbindungen an ein Abfrageportal zur klinischen Charakterisierung von COVID-19-Patient*innen angebunden [ 6 8 ]. Auf Basis dieser dezentralen COVID-19-Forschungsdatenrepositorien konnten wissenschaftliche Erkenntnisse zum Verlauf der COVID-19-Pandemie und zu ihren Auswirkungen auf die stationäre Versorgung in den UK bereits im Sommer 2020 gewonnen werden [ 9 – 11 ].…”
Section: Die Fünf Komponenten Der Num-forschungsdateninfrastrukturunclassified
“…Beyond this, the development work of the Network University Medicine COVID-19 Data Exchange Platform (CODEX) [ 5 ] project can be seamlessly integrated. In the CODEX project, based on prespecified requirements, a first test version of the envisaged feasibility tool (hereinafter referred to as feasibility tool v1) for simple queries has already been implemented and evaluated by potential end users regarding user-friendliness [ 6 - 8 ].…”
Section: Introductionmentioning
confidence: 99%