Guidelines for the effective use of entity–attribute–value modeling for biomedical databases

Dinu, Valentin; Nadkarni, Prakash M.

doi:10.1016/j.ijmedinf.2006.09.023

Cited by 92 publications

(66 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To deal with sparseness, many efforts are done at the physical layer [5,47,48], as well as the logical layer [1,10] of RDBMS. Various storage approaches suggested in RDBMS literature are detailed in the following subsections.…”

Section: Storage Approaches In Rdbms For Sparse Datasetmentioning

confidence: 99%

“…• Sparseness: Among the vast dimensions (attributes) of healthcare domain, only few are active for a patient [1]. For example, a patient with fever might not undergo any blood test, and thus, the corresponding attributes will contain null (sparse) values.…”

Section: Introductionmentioning

confidence: 99%

“…Moreover, every user is not aware of SQL. Even if a user is aware of SQL, the query corresponding to EAV will be highly complex and error-prone [1]. Thus, a Graphical User Interface (GUI) must be provided to the medical domain user for accessing Electronic Health Records (EHRs) that are stored in the database of a healthcare application.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Entity Attribute Value Style Modeling Approach for Archetype Based Data

2017

View full text Add to dashboard Cite

Entity Attribute Value (EAV) storage model is extensively used to manage healthcare data in existing systems, however it lacks search efficiency. This study examines an entity attribute value style modeling approach for standardized Electronic Health Records (EHRs) database. It sustains qualities of EAV (i.e., handling sparseness and frequent schema evolution) and provides better performance for queries in comparison to EAV. It is termed as the Two Dimensional Entity Attribute Value (2D EAV) model. Support for ad-hoc queries is provided through a user interface for better user-interaction. 2D EAV focuses on how to handle template-centric queries as well as other health query scenarios. 2D EAV is analyzed (in terms of minimum non-null density) to make a judgment about the adoption of 2D EAV over n-ary storage model of RDBMS. The primary aim of current research is to handle sparseness, frequent schema evolution, and efficient query support altogether for standardized EHRs. 2D EAV will benefit data administrators to handle standardized heterogeneous data that demands high search efficiency. It will also benefit both skilled and semi-skilled database users (such as, doctors, nurses, and patients) by providing a global semantic interoperable mechanism of data retrieval.

show abstract

Section: Storage Approaches In Rdbms For Sparse Datasetmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Entity Attribute Value Style Modeling Approach for Archetype Based Data

2017

View full text Add to dashboard Cite

show abstract

“…EAV is widely used in the medical and clinical information system as a general purpose means of knowledge representation. The Attribute-value pairs concept are an esteemed way of representing information on an object, originated on 1950s on the LISP association lists [16]. An example of attribute-value pairs showing a particular student information would be:…”

Section: Modelling Of Computer Platform Using Entity-attribute-valuementioning

confidence: 99%

Model Driven Atchitecture in to Support of Software Product Line

Elsawi¹,

Sahibuddin²

2015

IJCEE

View full text Add to dashboard Cite

Product management is focusing on variation description; as current and future possible market positioning, acceptable limitations, business opportunity, etc. On the other hand, the Architectural Modeling is concentrating on creation and description of software platform and how it extends and evolves to deliver and support all or any of these product management and product line scenarios. In product line engineering software features are always defined by the variability model. While the requirements specifications, architectural, design, implementation and testing are normally captured by the solution space. In this work we are utilizing the architectural modeling concept of the Model Driven Architecture (MDA) as a complementary of the software product line concerning the solution space part. Aiming to improve software quality and productivity the MDA principles has been adopt. We explicitly employed the Platform Model (PM) designed by the Entity-Attribute-Value (EAV) concept, to provision the transformation between Platform Specific Models (PSM) to the targeted platforms from side, and to manage the platforms diversity and volatility from other side. A case study presented to demonstrate the software productivity under the orthogonal relationship between the MDA and the SPL at the later solution space side.

show abstract

“…Three distinct conceptual modelling methods are often employed for database design: 1) the EntityRelationship (ER) model (Chen 1976;Kamble 2008); 2) Entity-Attribute-Value representation with classes and relationships (EAV/CR) model (Dinu and Nadkarni 2007;Lowe, Ferris et al 2009); and 3) Object-Oriented Database (OODB) (Trujillo, Palomar et al 2001). Although no consensus has been reached concerning modelling standards, we prefer the ER model due to its solid mathematic foundation, data structure semantic clarity, and data presentation transparency.…”

Section: Multidimensional Database Modellingmentioning

confidence: 99%