Deployments/develop.ohc.network
From OHC Network Wiki
More languages
More actions
develop.ohc.network is an actively maintained CARE development instance managed by Open Healthcare Network. It normally follows the current develop branches and may temporarily deploy feature branches to validate changes before they merge into develop.
Service overview
| Purpose | Development and feature-validation environment for CARE changes before they settle on the shared develop branches |
|---|---|
| Scope and users | Rolling-release CARE environment that may temporarily run feature branches |
| Data and criticality | Classification: Not documented Service tier: Development |
| Public endpoints | Frontend: https://develop.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 deploys from the selected frontend branch |
Repository Revision: develop (normally; feature branches may be deployed temporarily) |
| Backend | Provider: DigitalOcean App Platform DigitalOcean-native application deployment with automatic deploys from the selected backend branch |
Repository Revision: develop (normally; feature branches may be deployed temporarily) |
| 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_hello Backend stable
Reference backend plugin boilerplate.
Maintained by: ohcnetwork
Backend: repository
care_hello_fe Frontend stable
Reference frontend Care App example.
Maintained by: ohcnetwork
Frontend: repository
Delivery and change management
| CI/CD and deployment | DigitalOcean App Platform automatically deploys updates from the selected branches |
|---|---|
| Configuration source | DigitalOcean App Platform configuration and the selected CARE/care_fe branches; exact configuration repository or control plane remains to be documented |
| Release policy | Rolling release normally following the heads of ohcnetwork/care and ohcnetwork/care_fe develop; feature branches may be selected temporarily for pre-merge testing |
| Change records | Issue tracker, deployment history, or change log is not documented |
| Validation | Feature and integration testing before changes reach develop; 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 | This instance can temporarily diverge from develop while validating feature branches and may contain incomplete changes |
|---|---|
| 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 |