2021
DOI: 10.3233/shti210828
|View full text |Cite
|
Sign up to set email alerts
|

Semantics Management for a Regional Health Information System in Italy by CTS2 and FHIR

Abstract: An infrastructure for the management of semantics is being developed to support the regional health information exchange in Veneto – an Italian region which has about 5 million inhabitants. Terminology plays a key role in the management of the information fluxes of the Veneto region, in which the management of electronic health record is given great attention. An architecture for the management of the semantics of laboratory reports has been set up, adopting standards by HL7. The system has been initially deve… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 14 publications
0
2
0
Order By: Relevance
“…For this purpose, the concept of a terminology service was created to indicate a tool that allows us to provide access to terminology content through interfaces to read, query, maintain, and visualize the history of a specific terminology resource. The recent possible standard solution to define a terminology service, Application Programming Interface (API), is represented by the HL7 Fast Healthcare Interoperability Resources (FHIR) Terminology Service, already adopted in the literature [26][27][28][29]. The main limitation of the present approach is the possibility of establishing only hierarchical relations between concepts defined in the same code system and those mapped between concepts defined in different code systems.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…For this purpose, the concept of a terminology service was created to indicate a tool that allows us to provide access to terminology content through interfaces to read, query, maintain, and visualize the history of a specific terminology resource. The recent possible standard solution to define a terminology service, Application Programming Interface (API), is represented by the HL7 Fast Healthcare Interoperability Resources (FHIR) Terminology Service, already adopted in the literature [26][27][28][29]. The main limitation of the present approach is the possibility of establishing only hierarchical relations between concepts defined in the same code system and those mapped between concepts defined in different code systems.…”
Section: Discussionmentioning
confidence: 99%
“…In our work, we chose to address the problem of terminology management with a standard solution, specifically the Common Terminology Service Release 2 (CTS2), because it is services-based and we have already used it in several scenarios [13,[24][25][26]31,32]. As a main advantage, the use of CTS2 standard provides specifications useful to implement a set of operations to completely manage all aspects of CTS2 resources.…”
Section: Discussionmentioning
confidence: 99%