ArticlePDF Available

Abstract

The medical devices sector helps save lives by providing innovative health care solutions regarding diagnosis, prevention, monitoring, treatment, and alleviation. Medical devices are classified into 1 of 3 categories in the order of increasing risk: Class I, Class II, and Class III.1 Medical devices are distinguished from drugs for regulatory purposes based on mechanism of action. Unlike drugs, medical devices operate via physical or mechanical means and are not dependent on metabolism to accomplish their primary intended effect.
S9Abstract
Conclusions: Essentially, we found it possible to use Archetypes
and Templates to integrate a test set of intensive care data from 2
systems. By applying the openEHR approach for data modeling and
integration, detailed clinical models can be used for tasks such as
automated constraint checking, error reporting, data persistence, and
querying. Although medical scores such as the Glasgow Coma Scale
were a good fit for openEHR, voluminous data such as vital signs
and ventilation data needed some workarounds to work properly.
Especially, the demand of archetypes to be explicit about the meaning
of each data element might be problematic in some data integration
scenarios. On the one hand, this might be considered an advantage,
as it forces EDW developers and system analysts to work thoroughly.
On the other hand, this constraint might prevent pragmatic solutions
when a fast integration cannot be achieved or interpretation of data
can be conducted by the end-users. Although this work illustrates
some of the strengths and restrictions of the openEHR approach for
data integration tasks, our methodology is limited by the number
of used clinical concepts. A possible next step is the investigation of
the implications of openEHR-based information retrieval and the
semantic interpretation of data.
Key words: clinical information systems, data warehousing, detailed
clinical models, health care analytics, openEHR, secondary use.
Disclosure of Interest: None declared.
References
1. Dentler K, ten Teije A, de Keizer N, Cornet R. Barriers to the reuse
of routinely recorded clinical data: a field report. Stud Health Technol
Inform. 2013;192:313–317.
2. Chute CG1, Beck SA, Fisk TB, Mohr DN. The Enterprise Data Trust
at Mayo Clinic: a semantically integrated warehouse of biomedical
data. J Am Med Inform Assoc. 2010 Mar-Apr;17(2):131-5. http://
dx.doi.org/10.1136/jamia.2009.002691.
3. Goossen W, Goossen-Baremans A, van der Zel M. Detailed clinical
models: a review. Healthc Inform Res. 2010 Dec;16(4):201-14.
4. Beale T. Archetypes, constraint-based domain models for future-
proof information systems. Seattle, Washington, USA: Northeastern
University, Boston; 2002. pp. 16–32. (Eleventh OOPSLA workshop
on behavioral semantics: serving the customer: 2002.)
5. Frankel H. HL7 Working Group Meeting - Using Archetypes with HL7
Messages and Clinical Documents [PowerPoint presentation. 2011.
http://www.mz.gov.si/fileadmin/mz.gov.si/pageuploads/eZdravje/
Novice/gradiva_predstavitve_dogodkov/Open_EHR/7_integration.
pdf.
DEVELOPMENT OF MEDICAL DEVICES
D. Limaye
Hochschule Hannover, Hannover, Germany
Background: The medical devices sector helps save lives by provid-
ing innovative health care solutions regarding diagnosis, prevention,
monitoring, treatment, and alleviation. Medical devices are classified
into 1 of 3 categories in the order of increasing risk: Class I, Class II,
and Class III.1 Medical devices are distinguished from drugs for
regulatory purposes based on mechanism of action. Unlike drugs,
medical devices operate via physical or mechanical means and are
not dependent on metabolism to accomplish their primary intended
effect.2,3
Objectives: This study focused on regulations and differences in med-
ical device and pharmaceutical drug development. It also highlighted
the unique challenges faced while doing medical device development.
Methods: A US Food and Drug Administration and European
Medicines Agency website search was conducted to determine cur-
rent medical device regulations. A comprehensive literature search
was done from Google Scholar to determine the differences in drug
and medical device development.
Results: Designing well-controlled prospective clinical trials of
medical devices presents unique challenges that differ from those
faced in studies of pharmaceuticals. Clinical outcomes observed in
medical device studies, unlike drug trials, are influenced not only by
the product under evaluation and the patient but also by the skill
and discretion of the health care professional. Medically appropri-
ate alternative treatment regimens may not be available to provide
randomized, concurrent controls in device trials. Because devices are
often developed by small companies, financial constraints often limit
the new product development and testing.
Conclusions: Medical device development is faced with unique chal-
lenges. Managing the design issues in clinical trials and complying
with increasingly stringent regulatory guidelines is necessary to bring
new devices faster to market with reduced cost.
Key words: clinical trials, EMA, medical devices, USFDA.
Disclosure of Interest: None declared.
References:
1. What does it mean for FDA to “classify” a medical device?
USFDA. 2015. http://www.fda.gov/AboutFDA/Transparency/Basics/
ucm194438.htm.
2. Becker K. Clinical evaluation of medical devices. 2nd edition. 2006.
Humana Press Inc. USA. pp.3-4.
3. Abdel-aleem S. The Design and Management of Medical Device
Clinical Trials: Strategies and Challenges. John Wiley & Sons. 2011.
Pp.2-3.
QUALITY MANAGEMENT—NEW PERSPECTIVES
FOR MEDICAL DATA MANAGER
A. Haendel; and G. Michelson
University of Erlangen–Nuremberg, Erlangen, Germany
Increasingly, hospitals and other players in the health care sector will
inevitably compete in terms of quality. Interinstitutional and cross-
sectoral quality assurance has been pushed forward during recent
years. Institution-related outcomes are published and accessible to
the public. Due to new health laws, in the near future, quality results
of hospitals will not only be decisive for reimbursement increases or
price reductions of the remuneration but will also be a crucial factor
for a hospital’s survival. Hospitals that are not able to get quality
deficiencies under control may lose their public supply mandate.
Thus, the outcome of hospitals should be measured on the basis
of predefined quality indicators to reach the objectives described
earlier. Key indicators are, on the one hand, measures of medical
performance. In particular, these include, for example, the type and
numbers of surgical procedures as well as surgical complications in
a certain time period. Also included are structural statistics about
continuous medical education such as number of passed training
courses for medical doctors and nurses. Moreover, information about
patient safety are key indicators for quality assurance. Patient safety
indicators, for example, are the number of patient falls and side
effects of medication. These parameters have to be registered in a
structured form and in a fixed frequency. The method to provide
these indicators is a continuous comprehensive quality management,
including capturing and monitoring of all relevant data. This requires
the establishment of a professional operating system gaining all neces-
sary figures in daily clinical routine. Health information management
Chapter
Today, advances in science and technology may contribute to the resolution of medical devices for pediatric. This research focused on the development of the InfaWrap device; a tool to monitor neonate's heart rate and SpO2. InfaWrap is designed to help the clinicians and parents to observe the baby's heart rate and oxygen saturation. The InfaWrap device uses a pro mini Arduino as a microcontroller, a MAX30100 oximeter sensor to measure SpO2 and heart rate, and an LM35 to measure body temperature. Besides, we focus on the design and convenience wear criteria, including design characteristics, and structures to ensure the device is lightweight and more comfortable. The proposed InfaWrap device embedded an advanced wireless network sensor system. The data will be appeared in the mobile application installed on the doctor's or parent's mobile phone via Bluetooth module. Overall, based on three different babies as a subject in this study, we obtained that the InfaWrap device accuracy results reach the average of 96% for SpO2, 81 bpm for baby heart rate, and 36.4 °C for baby body temperature.KeywordsNeonatesMedical deviceMobile applicationInfaWrapPediatricsOximeter
Article
Full-text available
Today, clinical data is routinely recorded in vast amounts, but its reuse can be challenging. A secondary use that should ideally be based on previously collected clinical data is the computation of clinical quality indicators. In the present study, we attempted to retrieve all data from our hospital that is required to compute a set of quality indicators in the domain of colorectal cancer surgery. We categorised the barriers that we encountered in the scope of this project according to an existing framework, and provide recommendations on how to prevent or surmount these barriers. Assuming that our case is not unique, these recommendations might be applicable for the design, evaluation and optimisation of Electronic Health Records.
Conference Paper
Full-text available
Most information systems today are built using "single-level" methodologies, in which both informational and knowledge concepts are built into one level of object and data models. In domains characterised by complexity, large numbers of concepts, and/or a high rate of defini- tional change, systems based on such models are expensive to maintain and usually have to be replaced after a few years. However, a two-level methodology is possible, in which systems are built from information models only, and driven at runtime by knowledge-level concept definitions, or "archetypes". In this approach, systems can be built more quickly and last longer, whilst archetypes are authored directly by domain specialists, rather than IT personnel. Executed properly, the approach has the potential for creating future-proof systems and infor- mation. Work in the medical informatics domain on electronic health records (EHRs) has shown that a two-level methodology is implementable, makes for smaller systems, and empowers domain users.
Article
Full-text available
Due to the increasing use of electronic patient records and other health care information technology, we see an increase in requests to utilize these data. A highly level of standardization is required during the gathering of these data in the clinical context in order to use it for analyses. Detailed Clinical Models (DCM) have been created toward this purpose and several initiatives have been implemented in various parts of the world to create standardized models. This paper presents a review of DCM. Two types of analyses are presented; one comparing DCM against health care information architectures and a second bottom up approach from concept analysis to representation. In addition core parts of the draft ISO standard 13972 on DCM are used such as clinician involvement, data element specification, modeling, meta information, and repository and governance. SIX INITIATIVES WERE SELECTED: Intermountain Healthcare, 13606/OpenEHR Archetypes, Clinical Templates, Clinical Contents Models, Health Level 7 templates, and Dutch Detailed Clinical Models. Each model selected was reviewed for their overall development, involvement of clinicians, use of data types, code bindings, expressing semantics, modeling, meta information, use of repository and governance. Using both a top down and bottom up approach to comparison reveals many commonalties and differences between initiatives. Important differences include the use of or lack of a reference model and expressiveness of models. Applying clinical data element standards facilitates the use of conceptual DCM models in different technical representations.
Book
Highly praised in its first edition, Clinical Evaluation of Medical Devices: Principles and Case Studies, Second Edition has been expanded and updated to include the many innovations and clinical research methods that have developed since the first edition, as well as current information on the regulatory, legal, and reimbursement environment for medical devices. The book's deeply experienced authors summarize the key principles and approaches employed in medical device clinical trials and illustrate their uses in a revealing series of detailed, real-world case studies. Highlights include new information on the requirements and process for gaining reimbursement from Medicare and private insurers on new products-including case studies of research specifically designed for this purpose-and new statistical methods applied to medical device trials. Additional case studies provide examples of combination products, three-phase development models (i.e., feasibility, FDA approval, and Medicare reimbursement), and novel study designs. The cases demonstrate a wide range of designs that have been successfully applied to many different research problems, as well as to a variety of therapeutic or diagnostic products. Authoritative and highly practical, Clinical Evaluation of Medical Devices: Principles and Case Studies, Second Edition, provides a gold-standard resource for clinical professionals and regulatory specialists working at the forefront of new therapeutics, diagnostics, and medical device development and marketing today.
Article
Clinical trials tasks and activities are widely diverse and require certain skill sets to both plan and execute. This book provides professionals in the field of clinical research with valuable information on the challenging issues of the design, execution, and management of clinical trials, and how to resolve these issues effectively. It discusses key obstacles such as challenges to patient recruitment, investigator and study site selection, and dealing with compliance issues. Through practical examples, professionals working with medical device clinical trials will discover the appropriate steps to take.
Article
Mayo Clinic's Enterprise Data Trust is a collection of data from patient care, education, research, and administrative transactional systems, organized to support information retrieval, business intelligence, and high-level decision making. Structurally it is a top-down, subject-oriented, integrated, time-variant, and non-volatile collection of data in support of Mayo Clinic's analytic and decision-making processes. It is an interconnected piece of Mayo Clinic's Enterprise Information Management initiative, which also includes Data Governance, Enterprise Data Modeling, the Enterprise Vocabulary System, and Metadata Management. These resources enable unprecedented organization of enterprise information about patient, genomic, and research data. While facile access for cohort definition or aggregate retrieval is supported, a high level of security, retrieval audit, and user authentication ensures privacy, confidentiality, and respect for the trust imparted by our patients for the respectful use of information about their conditions.
Article
concepts from Analysis Domain concepts from Requirements Authors: Thomas Beale Page 13 of 69 Date of Issue:21/Aug/01 Copyright 2000 Thomas Beale email: thomas@deepthought.com.au web: www.deepthought.com.au Archetypes System Development Methodologies Rev 2.2.1 Shortcomings of the Classical Approach Problems with the classical modelling approach include: . The model encodes only the requirements found during the current development, along with best guesses about future ones. . Models containing both generic and domain concepts in the same inheritance hierarchy are problematic: the model can be unclear since very general concepts may be mixed with very specific ones, and later specialisation of generic classes is effectively prevented. The model is also not easily reusable in other domains. . Technical problems such as the "fragile base class" problem (See [9.]) must be understood and avoided both initially, and during maintenance. . It is often difficult to complete models satisfactorily, since the number of domain concepts may be large, and ongoing requirements gathering can lead to an explosion of domain knowledge, all of which has to be incorporated into the final model. In domains where the number of concepts is very large, such as health, this problem can retard software system completion significantly. . There may be a problem of semantic fitness. It is often not possible to clearly model domain concepts directly in the classes, methods and attributes of typical object formalisms. Domain concepts have significant variability, and often require constraints expressed in predicate logic to complete their definition. A more powerful "language" for domain concepts may be needed. See The Problem of Variability below. . Modelling can be logistically difficult t...
References: 1. What does it mean for FDA to "classify" a medical device? USFDA
  • H Frankel
Frankel H. HL7 Working Group Meeting -Using Archetypes with HL7 Messages and Clinical Documents [PowerPoint presentation. 2011. http://www.mz.gov.si/fileadmin/mz.gov.si/pageuploads/eZdravje/ Novice/gradiva_predstavitve_dogodkov/Open_EHR/7_integration. pdf. References: 1. What does it mean for FDA to "classify" a medical device? USFDA. 2015. http://www.fda.gov/AboutFDA/Transparency/Basics/ ucm194438.htm.