Limits...
Enabling flexible integration of healthcare information using the entity-attribute-value storage model.

Löper D, Klettke M, Bruder I, Heuer A - Health Inf Sci Syst (2013)

Bottom Line: Therefore, a digital patient care record is introduced to establish the foundation for integrating healthcare-related information.The time for traversing the results strongly depends on the number of documents.The underlying database structure is presented, the import process for extracting incoming reports is described and the export process for generating new outgoing standardized reports is briefly illustrated.

View Article: PubMed Central - PubMed

Affiliation: Database Research Group, University of Rostock, 18051 Rostock, Germany.

ABSTRACT

Background: For an optimal care of patients in home healthcare, it is essential to exchange healthcare-related information with other stakeholders. Unfortunately, paper-based documentation procedures as well as the heterogeneity between information systems inhibit a well-regulated communication. Therefore, a digital patient care record is introduced to establish the foundation for integrating healthcare-related information.

Methods: For the digital patient care record, suitable integration techniques are required that store data in a compact way and offer flexibility as well as robustness. For this purpose, a generic storage structure based on the entity-attribute-value (EAV) model is introduced. This storage structure fulfills the stated requirements and incoming information can be stored directly without any loss of data.

Evaluation results and discussions: First performance tests regarding the query response time are given in this paper. The tests measured the connection time, the query execution time, and the time for traversing the result set. The time for executing the query is lowest. The time for traversing the results strongly depends on the number of documents. A concept comparison to other integration techniques is also presented.

Conclusions: This approach offers flexibility concerning different standard types and the evolution in healthcare knowledge and processes. It also allows for highly sparse data to be stored in a compact way. The underlying database structure is presented, the import process for extracting incoming reports is described and the export process for generating new outgoing standardized reports is briefly illustrated.

No MeSH data available.


Storing the Example in the EAV Structure. The above example of a German ePflegebericht is stored into the shown tables. All the XML entities are stored in the relation Entity and their attributes are stored in the relation Attribute, respectively. The values are stored in the corresponding value relations. Each value tuple references one attribute and one entity tuple, respectively. A value also references the entry for the general source document information.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC4340778&req=5

Fig4: Storing the Example in the EAV Structure. The above example of a German ePflegebericht is stored into the shown tables. All the XML entities are stored in the relation Entity and their attributes are stored in the relation Attribute, respectively. The values are stored in the corresponding value relations. Each value tuple references one attribute and one entity tuple, respectively. A value also references the entry for the general source document information.

Mentions: Figure 4 displays how this document is mapped to the EAV storage structure. For simplification purposes, only those tables are shown which contain data from the example. Importantly, all the XML elements reside in the entity relation, and the XML attributes are stored in the attribute relation, respectively. The value relations contain the actual values along with references to the corresponding attribute, entity and source_doc entry.Figure 4


Enabling flexible integration of healthcare information using the entity-attribute-value storage model.

Löper D, Klettke M, Bruder I, Heuer A - Health Inf Sci Syst (2013)

Storing the Example in the EAV Structure. The above example of a German ePflegebericht is stored into the shown tables. All the XML entities are stored in the relation Entity and their attributes are stored in the relation Attribute, respectively. The values are stored in the corresponding value relations. Each value tuple references one attribute and one entity tuple, respectively. A value also references the entry for the general source document information.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC4340778&req=5

Fig4: Storing the Example in the EAV Structure. The above example of a German ePflegebericht is stored into the shown tables. All the XML entities are stored in the relation Entity and their attributes are stored in the relation Attribute, respectively. The values are stored in the corresponding value relations. Each value tuple references one attribute and one entity tuple, respectively. A value also references the entry for the general source document information.
Mentions: Figure 4 displays how this document is mapped to the EAV storage structure. For simplification purposes, only those tables are shown which contain data from the example. Importantly, all the XML elements reside in the entity relation, and the XML attributes are stored in the attribute relation, respectively. The value relations contain the actual values along with references to the corresponding attribute, entity and source_doc entry.Figure 4

Bottom Line: Therefore, a digital patient care record is introduced to establish the foundation for integrating healthcare-related information.The time for traversing the results strongly depends on the number of documents.The underlying database structure is presented, the import process for extracting incoming reports is described and the export process for generating new outgoing standardized reports is briefly illustrated.

View Article: PubMed Central - PubMed

Affiliation: Database Research Group, University of Rostock, 18051 Rostock, Germany.

ABSTRACT

Background: For an optimal care of patients in home healthcare, it is essential to exchange healthcare-related information with other stakeholders. Unfortunately, paper-based documentation procedures as well as the heterogeneity between information systems inhibit a well-regulated communication. Therefore, a digital patient care record is introduced to establish the foundation for integrating healthcare-related information.

Methods: For the digital patient care record, suitable integration techniques are required that store data in a compact way and offer flexibility as well as robustness. For this purpose, a generic storage structure based on the entity-attribute-value (EAV) model is introduced. This storage structure fulfills the stated requirements and incoming information can be stored directly without any loss of data.

Evaluation results and discussions: First performance tests regarding the query response time are given in this paper. The tests measured the connection time, the query execution time, and the time for traversing the result set. The time for executing the query is lowest. The time for traversing the results strongly depends on the number of documents. A concept comparison to other integration techniques is also presented.

Conclusions: This approach offers flexibility concerning different standard types and the evolution in healthcare knowledge and processes. It also allows for highly sparse data to be stored in a compact way. The underlying database structure is presented, the import process for extracting incoming reports is described and the export process for generating new outgoing standardized reports is briefly illustrated.

No MeSH data available.