Care Programme Wearables Procurement Specification
A care programme’s wearable specification is not a list of sensor counts or UI mock-ups. It is a binding framework for accountability across procurement, import, deployment and support — one that names who books which test, when sizing adjustments occur, how firmware updates are verified, and where clinical boundaries are drawn in writing. WingPhoenix AI publishes its factory policy to align with this need: every hardware revision carries a defined compliance scope, size-exchange window, MOQ tier and data-handling boundary. This article details how to embed those commitments directly into tender language, avoiding assumptions that surface only at customs, audit or incident review.
Size Provisioning and Exchange Protocol
Smart rings are sized products. For programmes requiring fit assurance across diverse user groups, specify that size kits ship before production begins, and unopened units in incorrect sizes may be exchanged only within the same production run — not across revisions or orders. Stocked sizes are 6–13; non-standard sizes require ODM tooling lead time and separate MOQ. The EN 1811 nickel release test applies exclusively to the skin-contact build of the ring, and is booked per hardware revision — it is not covered under CE RED or general RoHS screening. This requirement is detailed in the health smart ring and smart ring with charging case product pages.
Compliance Booking Per Revision, Not Model
Certification is not inherited. Each hardware revision — even minor PCB or antenna changes — requires its own lab booking for CE RED (EN 300 328, EN 301 489, EN 62368-1), FCC Part 15 B/C, UKCA on request, RoHS 3, REACH SVHC screening, battery UN38.3 + SDS, and EN 1811 where applicable. No certificate is “held” by WingPhoenix; instead, test scope is booked against the exact BOM and firmware version shipped. The CE RED document checklist outlines required evidence per submission. For service robots, add EMC and low-voltage scope, class 1 laser statement for LiDAR, and documented risk assessment — none of which fall under CE RED.
MOQ, Sampling and Lead Time Alignment
Procurement timelines collapse when MOQ tiers mismatch rollout phases. Standard MOQ is 500 units; custom packaging starts at 1,000; firmware or app white-label requires 2,000. Smart rings and companion robots have distinct thresholds: 1,000 and 50 units respectively. Samples ship in 3–5 days if stock-configured, or 7–15 days if configured — and sample cost is credited against mass production. Production lead times range from 25–35 days (standard), 30–40 days (education models) or 12–20 weeks (ODM tooling). All details are confirmed in the MOQ, sampling and lead times resource.
Data Handling and Clinical Boundary Language
Procurement language must prohibit supplier claims that devices monitor, detect, diagnose or alert for clinical conditions. Health metrics are wellness guidance only; translation output is reference-level; companion robots do not monitor falls or initiate emergency calls. These boundaries are factory policy — not optional disclaimers — and must appear verbatim in tender annexes and supplier agreements. They inform lab test scope, labelling, and end-user documentation. The Health & Wellness line and companion robot pages reflect this strict framing.
What This Specification Cannot Cover
This specification does not cover clinical validation reports, real-world efficacy studies, or third-party interoperability certifications (e.g., HL7 FHIR conformance, HIPAA-compliant hosting, or NHS Digital Data Security and Protection Toolkit alignment). WingPhoenix does not generate, hold or submit such reports. Importers must commission these separately — and verify that any claimed integration capability is tested against the exact firmware version deployed. A supplier citing “clinical readiness” without naming the specific report, issuing body and revision date should be disqualified. This limit is why procurement teams rely on the how we build and test page: it confirms what *is* documented, not what is promised.
Support, Warranty and Documentation Handover
Warranty is 12 months, with 2 % free replacement parts shipped with the order — not as call-in spares. QC gates (IQC / IPQC / FQC / OQC) apply at AQL 2.5 major and 4.0 minor. All documents — including CE RED, FCC, UKCA, RoHS 3, REACH SVHC, UN38.3, SDS and EN 1811 — are supplied per model and hardware revision. Firmware updates require joint sign-off on change logs and re-testing scope; no over-the-air update is applied without written confirmation. Full traceability is supported via the OEM/ODM services portal and referenced in the product catalogue.
| Requirement | What Must Be Specified in Tender | Factory Policy Reference |
|---|---|---|
| Size Exchange | Unopened wrong sizes exchanged only within same production run; size kit shipped pre-production | r1-ai-health-ring |
| CE RED Scope | Test booked per hardware revision — not model — including EN 300 328, EN 301 489, EN 62368-1 | CE RED checklist |
| Battery Documentation | UN38.3 test summary and SDS supplied per batch; watt-hour rating printed on each unit | how we build and test |
| Nickel Release | EN 1811 test booked for all skin-contact builds — separate from CE RED or RoHS | r2-smart-ring |
| Clinical Claims | Explicit prohibition of monitoring, detection, diagnosis or emergency-response language | k1-ai-companion-robot |
| Importer Duties | WEEE, BattG, DEEE/Triman, EORI/VAT responsibilities assigned to importer — not supplier | the journal |
| Firmware Updates | Change log sign-off and re-test scope required before OTA deployment | OEM/ODM services |
- Confirm size kit shipping schedule before signing MOQ commitment
- Require lab booking confirmation for EN 1811 before approving ring samples
- Verify UN38.3 and SDS match the exact battery revision in the BOM
- Insert clinical boundary language verbatim into tender Annex C
- Assign WEEE, BattG and VAT responsibility explicitly to importer in contract clause 4.2
- Book EMC and laser safety tests separately for service robots — not under CE RED
Procurement specifications for care programme wearables fail not from missing features, but from unallocated accountability: who books EN 1811, who holds WEEE registration, who signs off firmware changes. WingPhoenix publishes its factory policy so those handovers can be written, not assumed. To begin drafting your tender annexes, download the CE RED document checklist, review the MOQ, sampling and lead times guide, and schedule a compliance alignment call using the OEM/ODM services portal.
Questions buyers ask
What should a care programme’s tender require from a wearable supplier that goes beyond battery life or app interface?
It must define size exchange logistics, per-revision certification booking, firmware update responsibility, importer-held regulatory duties, and explicit limits on health claims.
How does finance assess risk when procuring wearables for a multi-site care programme?
By verifying MOQ alignment with rollout phasing, warranty terms covering replacement parts in-kind, and whether UN38.3 and SDS documentation are tied to each production batch.
Why did our distributor reject the sample ring shipment despite passing CE RED?
Because EN 1811 nickel release testing was not booked for that hardware revision — a requirement for all skin-contact items, regardless of CE RED scope.
What claim do most suppliers avoid naming in writing?
That no device monitors, detects, diagnoses or alerts for clinical conditions — a boundary enforced by factory policy and reflected in lab test scopes, not marketing copy.
Related: more on ai health monitoring · buyer guides · customisation tiers