Deployments/care.ohc.network
From OHC Network Wiki
More languages
More actions
care.ohc.network is an actively maintained CARE development instance managed by Open Healthcare Network. It follows the current develop branches of CARE backend and frontend through rolling, automatic releases.
Service overview
| Purpose | Continuously updated development instance for exercising the current integrated CARE codebase |
|---|---|
| Scope and users | Rolling-release CARE environment tracking upstream development |
| Data and criticality | Classification: Not documented Service tier: Development |
| Public endpoints | Frontend: https://care.ohc.network |
Governance and responsibility
| Accountable organisation | Open Healthcare Network |
|---|---|
| Platform operator | Open Healthcare Network |
| Supporting organisations | None documented |
| Service ownership | Clinical/product: Not documented Technical: Open Healthcare Network Data controller: Not documented |
| Support and escalation | Not documented |
| Commercial ownership | Billing owner: Not documented |
Application and infrastructure
| Component | Deployment details | Source and release |
|---|---|---|
| Frontend | Provider: DigitalOcean App Platform DigitalOcean-native application deployment with automatic rolling releases from the frontend develop branch |
Repository Revision: develop |
| Backend | Provider: DigitalOcean App Platform DigitalOcean-native application deployment with automatic rolling releases from the backend develop branch |
Repository Revision: develop |
| Database | Provider: DigitalOcean DigitalOcean-managed database service; engine, version, topology, and region remain to be documented |
Schema change process not documented |
| Object/file storage | Provider: DigitalOcean DigitalOcean-native storage; exact service and lifecycle remain to be documented |
Change process not documented |
| Runtime and network | Primary provider: DigitalOcean Region(s): Not documented Runtime/orchestrator: DigitalOcean App Platform |
Ingress, egress, DNS, CDN/WAF, and private connectivity not documented |
| Supporting services | Cache: Not documented Queue/broker: Not documented Search: Not documented |
Identity: Not documented Messaging: Not documented Other dependencies: Not documented |
CARE plugins
The list below is generated from the deployment-plugin inventory. Repository and maintainer data come from each plugin page; configuration must name flags or secret references only, never secret values.
care_state_hmis Backend active
State-level HMIS automation for government health department reporting.
Maintained by: 10bedicu
Backend: repository
care_token_display Backend active
Renders token display pages for patient queue management with auto-refresh.
Maintained by: ohcnetwork
Backend: repository
care_scribe Frontend + backend active
AI Voice Scribe for clinical transcription using OpenAI Whisper and Google Speech-to-Text.
Maintained by: 10bedicu
Backend: repository
Frontend: repository
care_abdm Frontend + backend active
Integration with India's Ayushman Bharat Digital Mission (ABDM) for health data exchange.
Maintained by: 10bedicu
Backend: repository
Frontend: repository
care_hcx Frontend + backend active
Health Claims Exchange (HCX) integration for insurance claim workflows.
Maintained by: 10bedicu
Backend: repository
Frontend: repository
care_nhcx Frontend + backend active
National Health Claims Exchange (NHCX) integration for government health scheme claims.
Maintained by: 10bedicu
Backend: repository
Frontend: repository
care_notifications Frontend + backend active
SMS and in-app notifications for patient booking and operational alerts.
Maintained by: ohcnetwork
Backend: repository
Frontend: repository
care_analytics_fe Frontend active
Analytics dashboards and reporting UI.
Maintained by: ohcnetwork
Frontend: repository
Delivery and change management
| CI/CD and deployment | DigitalOcean App Platform automatically deploys updates from the configured develop branches as a rolling release |
|---|---|
| Configuration source | DigitalOcean App Platform configuration and the CARE/care_fe develop branches; exact configuration repository or control plane remains to be documented |
| Release policy | Rolling release following the heads of ohcnetwork/care and ohcnetwork/care_fe develop |
| Change records | Issue tracker, deployment history, or change log is not documented |
| Validation | Development-instance validation; exact automated and manual checks remain to be documented |
Security, privacy, and compliance
| Identity and access | Application and platform security use DigitalOcean-native capabilities; authentication, authorization, and access-review procedures remain to be documented |
|---|---|
| Secrets management | DigitalOcean-native secret/configuration facilities; secret names, rotation, and ownership remain to be documented Do not place secret values on this wiki. |
| Encryption and boundaries | Encryption in transit/at rest, network boundaries, and key ownership are not documented |
| Audit and assurance | Audit trail, retention, reviewers, and security assessment are not documented |
| Privacy and retention | Purpose limitation, residency, retention, deletion, consent, and data-subject processes are not documented |
| Compliance | Applicable law, policy, agreements, and evidence location are not documented |
Observability and operations
| Health and monitoring | DigitalOcean-provided platform monitoring; dashboards, checks, and ownership remain to be documented |
|---|---|
| Alerting | DigitalOcean-provided platform alerting; routes and severity policy remain to be documented |
| Logs and traces | Collection, access, redaction, retention, and tracing are not documented |
| Service objectives | Availability target, SLIs/SLOs, capacity thresholds, and error budget are not documented |
| Runbooks | Not documented |
| Routine operations | Patching, certificate/domain renewal, scaling, housekeeping, and ownership are not documented |
Continuity and recovery
| Backups | DigitalOcean-provided backup capabilities; covered resources, schedule, retention, and restore ownership remain to be documented |
|---|---|
| Restore assurance | Last restore test, result, and evidence are not documented |
| Recovery objectives | RPO: Not documented · RTO: Not documented |
| Disaster recovery | Failure scenarios, alternate region/site, failover, and failback are not documented |
| Decommissioning | Shutdown approval, export, retention, deletion, DNS, and cost cleanup are not documented |
Risks, decisions, and review
| Known limitations and risks | As a rolling development instance, behavior may change whenever the upstream develop branches advance |
|---|---|
| Architecture decisions | Decision records and accepted trade-offs are not documented |
| Open actions | None documented |
| Review record | Status: draft Last reviewed: 2026-08-25 Review owner: Not documented |