74:, are working towards standardized vendor-neutral device integration systems. The IHE provides a single set of internationally harmonized medical device informatics and interoperability standards as a unitary reference point for the industry. The IHE collaborates with Continua Health Alliance regarding data exchange protocol and device specializations.
77:
The IHE Patient Care Device (PCD) Technical
Framework Volumes 1-3 defines the established standards profiles, such as the integration, transaction and semantic content profiles respectively for complete, enterprise-wide integration and interoperability of health information systems. Several profiles
39:
Adherence to standards ensures interoperability within a network of medical devices. In most cases, the clinical environment is heterogenous; devices are supplied by a variety of vendors, allowing for different technologies to be utilized. Achieving interoperability can be difficult, as data format
30:
Medical devices may be connected on wireless and wired networks. Wireless networks, including Wi-Fi, Wireless
Medical Telemetry Service, and Bluetooth, provide more ubiquitous coverage of connectivity, allowing uninterrupted monitoring of patients in transit. Wired networks are fast, stable, and
137:
Hospitals have many different makes and models of medical devices. Each department has different types of devices, and rarely does an entire hospital run the same brand device. Because of the large number of devices, and the varying formats that data is exchanged (RS-232, HL7, Bluetooth, WiFi),
164:- Patient and device identifying information is encoded within an RFID tag. This information is detected, and the clinician is prompted to confirm the patient-device association. RFID is a more efficient method of positive patient identification when there are multiple devices in use.
158:- Patient data is encoded within a bar-code on the patient's identification bracelet. Device identifying data is encoded within a bar-code attached to the device. Scanning the patient bar-code in conjunction with the medical device bar-code, ensures a patient-device association.
27:. The term is used interchangeably with biomedical device connectivity or biomedical device integration. By eliminating the need for manual data entry, potential benefits include faster and more frequent data updates, diminished human error, and improved workflow efficiency.
85:- supports publication of information from point-of-care medical devices to applications such as clinical information systems and electronic health record systems, using a consistent Health Level Seven version 2 (HL7 v.2) messaging format and device semantic content or
117:
semantic standards converting vendor specific terms into harmonized standard terms. It uses a set of tools (Excel spreadsheets & XML files) to map the proprietary semantics communicated by medical devices to a standard representation using
51:
enables the communication between medical devices and external information systems. This standard provides plug-and-play interoperability between devices, and facilitates the efficient exchange of data acquired at the point of care in all care
107:- supports communication of a 5-Rights validated medication delivery / infusion order (from Bar Code Medication Administration (BCMA) system, also known as Barcode Point of Care (BPOC) system, to an infusion pump or pump management system
347:
146:
Patient confidentiality can be compromised when the device data is transmitted to the wrong electronic health record. A positive patient identification at the point of care can be ensured through bar-code identifiers and
211:
320:
Rhoads, John G.; Cooper, Todd; Fuchs, Ken; Schluter, Paul; Zambuto, Raymond Peter (2010). "Medical device interoperability and the
Integrating the Healthcare Enterprise (IHE) initiative".
31:
highly available. Wired networks are usually more costly to install at first and require ongoing costs for maintenance, but allow connectivity of the organization in a closed environment.
292:
201:
Devices may have limited memory, necessitating the use of scaled back versions of operating systems, making it more difficult to utilize common security software.
192:
Due to tight regulations surrounding medical devices, upgrades to software and security installations must be approved by the manufacturer, resulting in delays.
396:
IHE International Inc. (2012). IHE Patient Care Device
Technical Framework, Volume 1 (IHE PCD TF-1): Integration Profiles (Vol. 10, pp. 1– 42). Retrieved from
128:
profile - specifies a mechanism for transmission, and processing of discrete data elements and report attachments associated with cardiac device observations.
296:
290:
Day, B., (2011). Standards for medical device interoperability and integration. Patient Safety & Quality
Healthcare, Jan/Feb. Retrieved from
173:
Security issues may arise in medical networking for many reasons. The following is a list of security challenges particular to medical devices:
67:
427:
McAlpine, B (2011). "Improving medical device connectivity. Both bar coding and RFID technologies can be applied to improve workflow".
40:
and encryption varies among vendors and models. The following standards enable interoperability between connected medical device.
277:
509:
59:
148:
504:
178:
71:
138:
Medical Device
Integration software has become a critical component to integrating this vital patient data.
411:
IHE International Inc. (2012). IHE.net
Technical Frameworks. August 16. Retrieved November 14, 2012, from
186:
372:
397:
95:- ensures the right alarm with the right priority to the right individuals with the right content.
24:
19:
is the establishment and maintenance of a connection through which data is transferred between a
480:
436:
325:
258:
182:
472:
62:(WLAN) in 2.4 GHz and 5 GHz frequency bands, utilizing the same basic protocol.
412:
370:
IHE International. (2012). IHE Patient Care Device . Retrieved
November 16, 2012, from
217:
119:
114:
46:
20:
249:
Witonsky, P (2012). "Leveraging EHR investments through medical device connectivity".
498:
195:
Device operating systems are often early generation and may no longer be supported.
55:
476:
228:
223:
484:
440:
329:
262:
463:
Wirth, Axel (2011). "Cybercrimes Pose
Growing Threat to Medical Devices".
78:
have applications in medical device connectivity including the following:
198:
Homogenous device environments facilitate rapid spread of computer virus.
348:"Medical Medical Device Interoperability Interoperability Inquiry"
86:
398:
http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Vol1.pdf
293:"Standards for Medical Device Interoperability and Integration"
66:
Regulatory organizations and industrial associations, such as
376:
212:
Association for the
Advancement of Medical Instrumentation
101:- supports a filtering mechanism for data transaction.
413:
http://www.ihe.net/Technical_Framework/index.cfm#pcd
126:Implantable Device – Cardiac – Observation (IDCO)*
142:Positive Patient Identification and Connectivity
346:Cooper, Todd; Rhoads, John (October 7, 2010).
315:
313:
278:"Pros and Cons of Wireless and Local Networks"
177:Medical devices often operate with commercial
169:Security Issues in Medical Device Connectivity
8:
465:Biomedical Instrumentation & Technology
322:Biomedical Instrumentation & Technology
189:, which place them at risk of cyber threat.
422:
420:
58:a/b/g/n are standards for implementing a
373:"IHE.net IHE Patient Care Device Domain"
353:. Integrating the Healthcare Enterprise.
458:
456:
454:
452:
450:
366:
364:
362:
360:
241:
407:
405:
341:
339:
68:Integrating the Healthcare Enterprise
7:
276:Brookstone, Alan (August 17, 2011).
23:, such as a patient monitor, and an
133:Medical Device Integration Software
105:Point-of-care Infusion Verification
14:
251:Healthcare Financial Management
83:Device Enterprise Communication
93:Alarm Communication Management
1:
162:Radiofrequency Identification
429:Health Management Technology
111:Rosetta Terminology Mapping
60:wireless local area network
35:Interoperability of devices
17:Medical device connectivity
526:
149:radiofrequency identifiers
477:10.2345/0899-8205-45.1.26
99:Subscribe to Patient Data
179:central processing units
72:Continua Health Alliance
156:Bar-code Identification
206:Relevant organizations
187:off-the-shelf software
70:(IHE) initiative and
231:(Health Informatics)
510:Health informatics
113:- is based on the
25:information system
183:operating systems
517:
489:
488:
460:
445:
444:
424:
415:
409:
400:
394:
388:
387:
385:
384:
375:. Archived from
368:
355:
354:
352:
343:
334:
333:
317:
308:
307:
305:
304:
295:. Archived from
288:
282:
281:
273:
267:
266:
246:
525:
524:
520:
519:
518:
516:
515:
514:
505:Medical devices
495:
494:
493:
492:
462:
461:
448:
426:
425:
418:
410:
403:
395:
391:
382:
380:
371:
369:
358:
350:
345:
344:
337:
324:. Suppl: 21–7.
319:
318:
311:
302:
300:
291:
289:
285:
275:
274:
270:
248:
247:
243:
238:
208:
171:
144:
135:
37:
12:
11:
5:
523:
521:
513:
512:
507:
497:
496:
491:
490:
446:
416:
401:
389:
356:
335:
309:
283:
268:
240:
239:
237:
234:
233:
232:
226:
221:
218:Health Level 7
215:
207:
204:
203:
202:
199:
196:
193:
190:
170:
167:
166:
165:
159:
143:
140:
134:
131:
130:
129:
123:
120:ISO/IEEE 11073
115:ISO/IEEE 11073
108:
102:
96:
90:
64:
63:
53:
47:ISO/IEEE 11073
36:
33:
21:medical device
13:
10:
9:
6:
4:
3:
2:
522:
511:
508:
506:
503:
502:
500:
486:
482:
478:
474:
470:
466:
459:
457:
455:
453:
451:
447:
442:
438:
434:
430:
423:
421:
417:
414:
408:
406:
402:
399:
393:
390:
379:on 2012-02-04
378:
374:
367:
365:
363:
361:
357:
349:
342:
340:
336:
331:
327:
323:
316:
314:
310:
299:on 2013-01-31
298:
294:
287:
284:
279:
272:
269:
264:
260:
256:
252:
245:
242:
235:
230:
227:
225:
222:
219:
216:
213:
210:
209:
205:
200:
197:
194:
191:
188:
184:
180:
176:
175:
174:
168:
163:
160:
157:
154:
153:
152:
150:
141:
139:
132:
127:
124:
121:
116:
112:
109:
106:
103:
100:
97:
94:
91:
88:
84:
81:
80:
79:
75:
73:
69:
61:
57:
54:
52:environments.
50:
48:
43:
42:
41:
34:
32:
28:
26:
22:
18:
471:(1): 26–34.
468:
464:
432:
428:
392:
381:. Retrieved
377:the original
321:
301:. Retrieved
297:the original
286:
271:
254:
250:
244:
172:
161:
155:
145:
136:
125:
110:
104:
98:
92:
82:
76:
65:
44:
38:
29:
16:
15:
435:(5): 18–9.
257:(8): 50–3.
56:IEEE 802.11
499:Categories
383:2012-12-12
303:2012-12-10
236:References
229:ISO/TC 215
224:CEN/TC 251
122:semantics.
485:21322805
441:21650134
330:20225710
263:22931026
89:profile.
483:
439:
328:
261:
214:(AAMI)
351:(PDF)
220:(HL7)
185:, or
87:DICOM
481:PMID
437:PMID
326:PMID
259:PMID
45:CEN
473:doi
151:.
501::
479:.
469:45
467:.
449:^
433:32
431:.
419:^
404:^
359:^
338:^
312:^
255:66
253:.
181:,
487:.
475::
443:.
386:.
332:.
306:.
280:.
265:.
49:*
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.