Integration Specifications
Aranga is designed for flexible integration across deployment scenarios, from OEM device embedding to enterprise health system deployments.
Data Requirements
Minimum viable input set and optional signals for enhanced performance.
Required Inputs
Optional Inputs
Timing Requirements
- • Timestamps required for all inputs (as-of-time semantics)
- • System handles irregular sampling intervals
- • Minimum recommended: vital signs every 1-5 minutes
Output Specification
Deployment Options
Cloud API
Hosted inference endpoint
Health system integration
- REST API (JSON)
- Standard authentication
- SLA available
Edge Gateway
On-premise container
Low-latency, data residency
- Docker/Kubernetes
- ~2GB RAM
- Air-gapped option
Device SDK
Embedded library
OEM monitor integration
- ARM64/x86_64
- ~500MB footprint
- C++/Python bindings
Interfaces
REST API
Standard web integration with JSON payloads
gRPC
Low-latency streaming for embedded applications
HL7 FHIR R4
Resource mappings for Observation, RiskAssessment
HL7v2
ADT/ORU message handling guidance provided
What We Need From Partners
To scope an integration, we require the following information:
Pilot Engagement Outline
Our standard engagement process for new partner evaluations.
Retrospective Validation
Duration: 4-8 weeks
- Partner provides historical dataset
- Aranga runs evaluation against partner data
- Joint review of performance metrics
- Comparison with existing EWS if applicable
Silent Prospective Deployment
Duration: 8-12 weeks
- Integration into partner environment
- System runs in parallel (no clinical alerts)
- Performance monitoring and calibration
- Data quality assessment
Clinical Utility Assessment
Duration: TBD with partner
- Controlled clinical deployment
- Alarm burden and workflow impact measurement
- User feedback collection
- Prospective outcome tracking (if IRB approved)
Start the Integration Discussion
Contact us to discuss your integration requirements and receive detailed technical documentation under NDA.