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

Evaluation of software maintainability with openEHR – a comparison of architectures

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0
2

Year Published

2016
2016
2021
2021

Publication Types

Select...
7
3

Relationship

0
10

Authors

Journals

citations
Cited by 22 publications
(10 citation statements)
references
References 11 publications
0
8
0
2
Order By: Relevance
“…The openEHR specifications aim at accommodating new requirements primarily at the AM (archetype and template) level without the need to change the RM and its associated storage mechanism, thus requiring fewer changes in the application code and persistence mechanism [ 9 ]. This approach also promotes semantic interoperability between systems based on the shared RM, configured using (partly) shared archetypes and templates, but the interoperability aspect is not the focus of this paper.…”
Section: Introductionmentioning
confidence: 99%
“…The openEHR specifications aim at accommodating new requirements primarily at the AM (archetype and template) level without the need to change the RM and its associated storage mechanism, thus requiring fewer changes in the application code and persistence mechanism [ 9 ]. This approach also promotes semantic interoperability between systems based on the shared RM, configured using (partly) shared archetypes and templates, but the interoperability aspect is not the focus of this paper.…”
Section: Introductionmentioning
confidence: 99%
“…Academic application frameworks explore the potential of ODMs within EHR systems. GastrOS [35], for example, developed an openEHR based endoscopic reporting application that is capable of dynamically generating the graphical user interfaces (GUI) from underlying domain knowledge models. EHRServer [36] provides a Service-oriented, REST based, openEHR repository for clinical data.…”
Section: Resultsmentioning
confidence: 99%
“…Whether or not the maintainability of a software can be reflected in the costs and efforts required to accomplish this task. The way the software is developed, including the type of architecture and language used, can improve its maintainability (25) .…”
Section: Discussionmentioning
confidence: 99%