2019 International Conference on Wireless and Mobile Computing, Networking and Communications (WiMob) 2019
DOI: 10.1109/wimob.2019.8923179
|View full text |Cite
|
Sign up to set email alerts
|

Use of HL7 FHIR to structure data in epilepsy self-management applications

Abstract: The expansion of health infrastructure to support the networking of actors in the healthcare system is rapidly growing and is forced by law in several nations. The solutions are based on international standards to ensure interoperability of existing and new health applications and future viability. In the EPItect project, a telemedicine infrastructure for epilepsy care was developed. This paper presents part of the conceptual work and focuses on the structural and semantic standardization of epilepsy data base… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2021
2021
2022
2022

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 18 publications
0
2
0
Order By: Relevance
“…We obtained 11 categories for FHIR implementation. From a platform point of view, we considered the implementation of mobile/tablet apps [ 3 , 9 , 28 , 35 , 39 , 51 , 57 , 60 , 65 , 70 , 72 , 77 , 82 ], standalone apps/servers [ 3 , 23 , 51 , 58 , 61 ], web services/API [ 3 , 11 , 14 , 26 , 34 , 36 , 40 , 48 , 53 , 56 , 71 , 78 ], and web-based tools/applications [ 18 , 26 , 37 , 40 , 42 , 46 , 55 , 69 , 78 ] categories. From a conceptual framework, we considered the categories of general FHIR implementation [ 48 , 59 ], using SMART on FHIR [ 3 , 14 , 22 , 31 ], HL7 API (HAPI)-FHIR server/library/applications [ 14 , 16 , 20 , 32 , 34 - 36 , 40 , 43 , 51 , 54 , 55 , 73 , 76 , 81 , 82 ], and FHIR general framework [ 14 , 40 ,…”
Section: Resultsmentioning
confidence: 99%
“…We obtained 11 categories for FHIR implementation. From a platform point of view, we considered the implementation of mobile/tablet apps [ 3 , 9 , 28 , 35 , 39 , 51 , 57 , 60 , 65 , 70 , 72 , 77 , 82 ], standalone apps/servers [ 3 , 23 , 51 , 58 , 61 ], web services/API [ 3 , 11 , 14 , 26 , 34 , 36 , 40 , 48 , 53 , 56 , 71 , 78 ], and web-based tools/applications [ 18 , 26 , 37 , 40 , 42 , 46 , 55 , 69 , 78 ] categories. From a conceptual framework, we considered the categories of general FHIR implementation [ 48 , 59 ], using SMART on FHIR [ 3 , 14 , 22 , 31 ], HL7 API (HAPI)-FHIR server/library/applications [ 14 , 16 , 20 , 32 , 34 - 36 , 40 , 43 , 51 , 54 , 55 , 73 , 76 , 81 , 82 ], and FHIR general framework [ 14 , 40 ,…”
Section: Resultsmentioning
confidence: 99%
“…In existing concepts, the purpose, focus and maturity level vary. The systems are used in rehabilitation [32,33], in disease management programs for chronic diseases [34][35][36], in physiotherapy [37], as well as in behavioural research [38][39][40]. The purpose of these systems range from support in the implementation of therapy [41] to the monitoring of medical studies [42,43] and the use as a communication medium between patient and HSP [44].…”
Section: Introductionmentioning
confidence: 99%