2015 IEEE Symposium on Product Compliance Engineering (ISPCE) 2015
DOI: 10.1109/ispce.2015.7138703
|View full text |Cite
|
Sign up to set email alerts
|

Levels of conceptual interoperability model for healthcare framework for safe medical device interoperability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 26 publications
(18 citation statements)
references
References 3 publications
0
12
0
Order By: Relevance
“…state, context, change of either) and have discussed where this information comes from, including approaches to capture information and why the information in the device model is necessary for safety. The paper has described an approach to achieve safe medical device PnP using comprehensive device models that are “standardized”-characterized by dynamic interoperability between devices and conceptual interoperability within the organization utilizing the levels of interoperability concepts of Tolk and Muguira [1] , Turnitsa [2] , and Robkin et al [3] . And lastly the paper proposes that shared clinical scenarios enable developers to be conceptually interoperable, sharing the same goals, constraints, and processes which is necessary for their work product to achieve dynamic interoperability.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…state, context, change of either) and have discussed where this information comes from, including approaches to capture information and why the information in the device model is necessary for safety. The paper has described an approach to achieve safe medical device PnP using comprehensive device models that are “standardized”-characterized by dynamic interoperability between devices and conceptual interoperability within the organization utilizing the levels of interoperability concepts of Tolk and Muguira [1] , Turnitsa [2] , and Robkin et al [3] . And lastly the paper proposes that shared clinical scenarios enable developers to be conceptually interoperable, sharing the same goals, constraints, and processes which is necessary for their work product to achieve dynamic interoperability.…”
Section: Discussionmentioning
confidence: 99%
“…The standard ISO/IEC 10746-2-2009, RM-ODP Reference Model Open Distributed Processing defines a model in which the objects in the system identified from the clinical scenarios, the interfaces, their interaction points, and the behaviors of each object (a behavior is a collection of actions together contained with a set of constraints) are determined. To achieve safe plug-and-play dynamic interoperability, device and patient states, and use context must also be gathered and exchanged [3] .…”
Section: Determining Relevant Attributes Of a Device Model Related Tomentioning
confidence: 99%
See 1 more Smart Citation
“…This ecosystem includes system architecture requirements, interface specifications, nomenclatures and test methods. To achieve safe and effective interoperability 22 , these requirements should be applied to all of the components in the medical device ecosystem. A “blueprint” or “roadmap,” developed by a broad coalition, is needed to connect the existing patchwork of standards that try to address those needs.…”
Section: Clinical Needs and Other Driversmentioning
confidence: 99%
“…5 Technical inter-operability is responsible for the infrastructure and ensures the use of the same data on different devices. 6 Semantic interoperability is responsible for the unambiguous understanding of data by both the sender and the recipient. It uses specific codes and standard templates that constrain the possible number of message types transferred.…”
Section: Introductionmentioning
confidence: 99%