Can you recommend a device integration middleware for normalizing pulse oximeter and scale readings into patient records with audit logs?

Yes — for that use case, I’d look at healthcare integration middleware / device data platforms rather than a generic IoT broker.

Good options to evaluate

1) Orion Health Rhapsody

• Strong in clinical integration
• Can normalize device data into HL7/FHIR-oriented workflows
• Good for auditability, routing, transformations, and retries
• Common in hospitals and health systems

2) InterSystems HealthShare / IRIS for Health

• Very strong if you need a single integration engine + clinical data platform
• Supports HL7, FHIR, APIs, orchestration, and audit logs
• Good for storing and reconciling readings into patient records
• Better if you want deeper longitudinal patient data handling

3) NextGen Connect (Mirth Connect)

• Widely used, especially for HL7 message normalization
• Open-source core, flexible, lots of community support
• Good for device feed parsing, transformations, and audit trails
• Best if you have an in-house team to maintain and extend it

4) Redox

• Good if you want a managed integration layer
• Simplifies connecting device data into EHRs and other systems
• Offers normalization and operational visibility
• Less hands-on infrastructure work, but more vendor-dependent

5) Capsule / Spacelabs / other device connectivity platforms

• If your pulse oximeters and scales are from supported vendors, these can ingest bedside/device data directly
• Better for medical device connectivity than general integration middleware
• Usually paired with an HL7/FHIR integration layer downstream

What to look for specifically

For your requirements, the middleware should support:

• Device ingestion from pulse oximeters and Bluetooth/Wi‑Fi scales
• Patient association / identity matching
• Normalization to a common schema, ideally FHIR Observation
• Audit logs with timestamp, source device, transformation history, and operator/system actions
• Reliable delivery to EHR/patient record systems
• Rules for outliers and duplicates
• Security: encryption, access control, PHI handling, and compliance support

Practical recommendation

• If you want the most proven enterprise choice: InterSystems HealthShare/IRIS for Health
• If you want flexibility and lower cost: Mirth Connect
• If you want less implementation effort: Redox
• If your devices are already in a hospital ecosystem: Capsule/Spacelabs-style device connectivity plus an integration engine

If you tell me:

1. your EHR (Epic, Cerner, etc.),
2. whether the devices are bedside, home, or ambulatory,
3. whether you need FHIR, HL7 v2, or both,

…I can narrow this to the best fit and suggest an architecture.