Medical Applications User Guide (pdf) - Freescale Semiconductor
Medical Applications User Guide (pdf) - Freescale Semiconductor
Medical Applications User Guide (pdf) - Freescale Semiconductor
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
3.19<br />
Standard <strong>Medical</strong><br />
USB Communication<br />
For USB communication, two main standards<br />
must be considered:<br />
• IEEE ® 11073, which provides structure to<br />
the communication interface<br />
• Personal health care device class (PHDC),<br />
which is a standard implementation of USB<br />
for medical devices<br />
The advantage of designing medical<br />
applications with a dedicated medical stack<br />
instead of a conventional USB stack is that<br />
a medical USB stack is designed specifically<br />
for medical USB devices. It eases medical<br />
application data exchange because it has a<br />
specific device specialization layer. Designing<br />
medical applications under a conventional<br />
USB stack may not provide the added value<br />
of medical organizations’ certifications.<br />
Three main factors need to be considered<br />
when selecting a particular USB connectivity<br />
software implementation for medical devices.<br />
1. Standardization: The solution is based<br />
on well-known standards in the industry.<br />
This helps to ensure success and proper<br />
introduction of the product to the market.<br />
2. Connectivity: The implementation allows<br />
connecting multiple devices from different<br />
vendors within an ecosystem topology.<br />
A connectivity-friendly environment is<br />
sustained by a robust and easy-to-use<br />
software stack.<br />
3. Portability: Multi-device independent<br />
layered architecture eases porting of code<br />
among devices. Selecting a hardware<br />
vendor with a broad portfolio is key to<br />
ensure customization and product roadmap<br />
establishment.<br />
Software architecture ensures code<br />
robustness, portability and reliability in<br />
embedded systems development.<br />
Figure 3-23: Broadband Block Diagram<br />
Figure 3-20: Broadband Block Diagram<br />
Pedometer<br />
Weight<br />
Scale<br />
Blood-<br />
Pressure<br />
Cuff<br />
Fitness<br />
Equipment<br />
Medication<br />
Tracking<br />
Pulse<br />
Ox<br />
Home Portable <strong>Medical</strong><br />
Table 3-1. <strong>Freescale</strong> MCU/MPU Families that Support the USB Personal Health Care Device<br />
SOC Use Case<br />
S08<br />
MC9S08MM128 PAN device<br />
MC9S08JM16 Low-end PAN device<br />
MC9S08JM60 PAN device<br />
MC9S08JS16<br />
ColdFire V1<br />
Low-end PAN device<br />
MCF51JM128 PAN device, hybrid device, application hosting device<br />
MCF51MM256 PAN device, hybrid device, application hosting device<br />
MCF51JE256 PAN device, hybrid device, application hosting device<br />
MCF51(JF/JU)128<br />
ColdFire V2<br />
PAN device, hybrid device, application hosting device<br />
MCF5225x<br />
ARM<br />
PAN device, hybrid device, application hosting device<br />
® Cortex-M4<br />
Kinetis KL2x, KL4x PAN device, hybrid device, application hosting device<br />
Kinetis MK20, MK40, MK50 and MK60<br />
ARM i.MX<br />
PAN device, hybrid device, application hosting device<br />
MCIMX233 PAN device, application hosting device<br />
MCIMX28x PAN device, application hosting device<br />
MCIMX51x Application hosting device<br />
freescale .com/medical 21<br />
Implant<br />
USB Personal Health Care<br />
Device Class Specification<br />
Digital<br />
Home<br />
Cell Phone<br />
Personal Health<br />
System<br />
PC<br />
Internet<br />
Health Care<br />
Provider<br />
Service<br />
Disease<br />
Management<br />
Service<br />
Personal<br />
Health Record<br />
Service<br />
Implant<br />
Monitoring<br />
Service
Change language