Generic screen representations for future-proof systems, is it possible?

Linden, Helma van der; Austin, Tony; Talmon, Jan L.

doi:10.1016/j.cmpb.2009.03.003

Cited by 13 publications

(9 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To achieve a high level of usability, a separate visualization knowledge layer could be added that specifies a suitable way of presenting each archetype node in a form. Van der Linden et al presented a corresponding approach that distinguishes content-related, localized, and device-related presentation knowledge [35]. Kopanitsa proposed a presentation layer that considers different views for different users and devices [36], while Atalag et al relied on a set of graphical user interface directives to adjust the aesthetics and visual behaviour of generated forms [37].…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience

Duftschmid

Chaloupka

Rinner

2013

BMC Med Inform Decis Mak

View full text Add to dashboard Cite

BackgroundThe dual model approach represents a promising solution for achieving semantically interoperable standardized electronic health record (EHR) exchange. Its acceptance, however, will depend on the effort required for integrating archetypes into legacy EHR systems.MethodsWe propose a corresponding approach that: (a) automatically generates entry forms in legacy EHR systems from archetypes; and (b) allows the immediate export of EHR documents that are recorded via the generated forms and stored in the EHR systems’ internal format as standardized and archetype-compliant EHR extracts. As a prerequisite for applying our approach, we define a set of basic requirements for the EHR systems.ResultsWe tested our approach with an EHR system called ArchiMed and were able to successfully integrate 15 archetypes from a test set of 27. For 12 archetypes, the form generation failed owing to a particular type of complex structure (multiple repeating subnodes), which was prescribed by the archetypes but not supported by ArchiMed’s data model.ConclusionsOur experiences show that archetypes should be customized based on the planned application scenario before their integration. This would allow problematic structures to be dissolved and irrelevant optional archetype nodes to be removed. For customization of archetypes, openEHR templates or specialized archetypes may be employed. Gaps in the data types or terminological features supported by an EHR system will often not preclude integration of the relevant archetypes. More work needs to be done on the usability of the generated forms.

show abstract

Section: Discussionmentioning

confidence: 99%

“…To achieve this, approaches based on a separate visualization knowledge layer for archetypes may be employed [35-37]. …”

Section: Discussionmentioning

confidence: 99%

Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience

Duftschmid

Chaloupka

Rinner

2013

BMC Med Inform Decis Mak

View full text Add to dashboard Cite

show abstract

“…The archetype typically does not record such clinical knowledge. To do so would require another formalism (van der Linden et al, 2009). Although the object model forms the basis of the standard, most real archetypes are delivered in an ADL source file that is expected to be self-contained and have a fixed scope.…”

Section: Archetype Definition Languagementioning

confidence: 99%

Patterns: a simple but expressive data modelling formalism

Austin¹,

Sun²,

Lea

et al. 2016

IJKEDM

Self Cite

View full text Add to dashboard Cite

The creation of a clinical application requires models that describe the structure of data in a way that can be displayed, exchanged and stored. A number of approaches for this have been proposed and are in widespread use. However, these are often complex and/or have shortcomings in the breadth of data that they are able to represent. The annotations facility provided by many computer languages could be used to include information shaping the development and run-time behaviour of a clinical application. If this were comprehensive, then annotations alone would be sufficient for conceptual modelling. A model for representing such annotations is presented and some examples shown and discussed. The paper concludes that such a formalism is simple to use while developing semantic concepts but is capable of representing information from many models simultaneously. It is well suited to the needs of clinical teams seeking consensus on the structure of records.

show abstract

“…The characterization (▶ Table 2) of the visualization methods applied in the reviewed projects was based on the results and conclusions sections of the papers [24][25][26][27][28][30][31][32][33][34][35][36][37][38].…”

Section: Characterization Of the Visualization Methodsmentioning

confidence: 99%

“…The experience collected by the reviewed projects will be used as a basis for defining the requirements to the visual medical concepts for the ISO 13606 data model. The review showed that the presentation data should be stored separately from the medical data [31,32]. The most capable technology used in the reviewed projects is XML -an open standard that allows easy access and transformation of the data.…”

Section: Implementation Technologiesmentioning

confidence: 99%

Visualization of Medical Data Based on EHR Standards

Kopanitsa

Hildebrand²,

Stausberg³

et al. 2013

Methods Inf Med

View full text Add to dashboard Cite

SummaryBackground: To organize an efficient interaction between a doctor and an EHR the data has to be presented in the most convenient way. Medical data presentation methods and models must be flexible in order to cover the needs of the users with different backgrounds and requirements. Most visualization methods are doctor oriented, however, there are indications that the involvement of patients can optimize healthcare. Objectives: The research aims at specifying the state of the art of medical data visualization. The paper analyzes a number of projects and defines requirements for a generic ISO 13606 based data visualization method. In order to do so it starts with a systematic search for studies on EHR user interfaces. Methods: In order to identify best practices visualization methods were evaluated according to the following criteria: limits of application, customizability, re-usability. The visualization methods were compared by using specified criteria. Results: The review showed that the analyzed projects can contribute knowledge to the development of a generic visualization method. However, none of them proposed a model that meets all the necessary criteria for a re-usable standard based visualization method. The shortcomings were mostly related to the structure of current medical concept specifications. Conclusion:The analysis showed that medical data visualization methods use hardcoded GUI, which gives little flexibility. So medical data visualization has to turn from a hardcoded user interface to generic methods. This requires a great effort because current standards are not suitable for organizing the management of visualization data. This contradiction between a generic method and a flexible and user-friendly data layout has to be overcome.

show abstract

Generic screen representations for future-proof systems, is it possible?

Cited by 13 publications

References 7 publications

Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience

Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience

Patterns: a simple but expressive data modelling formalism

Visualization of Medical Data Based on EHR Standards

Contact Info

Product

Resources

About