BioArc architecture and infrastructure
BioArc brings patient services, clinical work, center management and research around connected data. Dedicated deployment can run on the institution’s infrastructure, with its own modules, permissions and integrations.
Technology
The diagram explains layer responsibilities. External services join the workflow only when configured and authorized.
Web workspace and BioVisit
HAProxy · Nginx · PHP-FPM
Admission · Visits · Prescriptions · Records · Inpatient care · Registries
HIS, PACS, insurers, payment gateways and SMS, according to the center’s available services and permissions.
Insurers and APIs
Prescribing in BioArc goes beyond recording medication. Social Security and Iran Health Insurance integrations connect eligibility checks, prescription submission, responses and tracking codes to the visit workflow.
The physician records prescriptions and services in the same workspace, with physician and institution identity carried through the integration.
Requests reach the destination through BioArc’s shared outbound gateway; API differences are handled by the integration layer.
Service responses, submission status and tracking codes become available for the next steps in the application.
When prescriptions are submitted through the BioArc gateway, institutions do not need to register a separate IP or obtain separate software-connection approval from Social Security, Health Insurance and other services covered by that gateway. BioArc coordinates the connection path, which can be enabled for both Standalone and As Service deployments.
This benefit concerns the technical connection path. Physician authentication and professional accounts, institutional insurance contracts and service eligibility remain subject to insurer requirements.
Eligibility checks, supported medication and service submissions, tracking-code retrieval and prescription lookup use insurer-specific service paths. The insurer response determines submission outcome; a locally saved prescription alone does not establish insurer acceptance.
Integration adapters handle authentication, request/response formats and identifier mapping for each service. HIS, PACS, Ministry of Health referral scheduling, payments and SMS connections are scoped to available APIs. Institutional IT teams can review exchange paths and error behavior in the technical workshop.
Referral pathways
BioArc takes an integrated approach to referrals, linking family physicians, specialists and institutions to everyday care. A referral is more than a number: inboxes, appointments, visit information and feedback form a traceable care pathway.
Retrieve allowed referral pathways, referral lists and details from insurer services, using patient and referral identifiers where supported.
Manage Ministry of Health referral appointments and capacity, submit appointment times and retrieve status, linking referrals to patient admission.
Retrieve referral and prescription details, record the visit and use referral-prescription services according to insurer support and physician access, alongside the patient record.
Submit or retrieve feedback and diagnoses through supported services, track referral status and review operational reports to support follow-up care.
Referral and feedback coverage varies by insurer and institution. Enabled services, physician access and referral-scheduling integration are defined during onboarding.
Open-source foundation
BioArc infrastructure uses open-source technologies without requiring separate commercial licenses for the listed components. Analytics, long-lived workers and key management are enabled according to deployment needs.
| Technology | Role in the platform | Open-source edition and license |
|---|---|---|
| Linux | Server services and infrastructure management | GPL / open-source distribution ↗ |
| HAProxy | Route and balance incoming traffic across web services according to the deployment topology | GPLv2 / LGPL ↗ |
| Nginx | Serve web content and route requests to application services | BSD ↗ |
| PHP / PHP-FPM | Application logic and web-request processing | PHP License ↗ |
| Yii | Application structure, request control and data access | BSD ↗ |
| Swoole | Run PHP services with long-lived workers in deployments using this runtime | Apache-2.0 ↗ |
| MariaDB Community | Store structured patient and operational data | GPLv2 ↗ |
| Valkey | Caching, session state and message/event coordination in the in-memory data layer | BSD-3-Clause ↗ |
| ClickHouse | Analytics and aggregate reporting where the analytical layer is enabled | Apache-2.0 ↗ |
| OpenBao | Key management and BioWork message-content encryption in Transit-enabled configurations | MPL-2.0 ↗ |
| Restic | Create and restore encrypted backup snapshots; data, file and configuration coverage follows the backup plan | BSD-2-Clause ↗ |
| rclone | Connect Restic backup repositories to remote storage | MIT ↗ |
BioArc software, implementation, hosting and support follow the contract. External SMS, payments and optional commercial products have their own terms and costs. Infrastructure versions and licenses are specified in the deployment plan.
The application and database can run on university or hospital infrastructure. Domain, branding, network, technical access and maintenance responsibilities are agreed with IT.
The hosting plan defines capacity, monitoring, backups and support. Application, database and file-service separation is designed for workload and institutional requirements.
Accounts, roles, centers and wards define viewing and recording scope. Support access and permission changes follow institutional policy.
Caching and WebSocket communication coordinate state and messages. Scheduled work supports background processing and maintenance alongside interactive requests.
Restic manages encrypted backup snapshots, with rclone connecting to remote storage. Database, configuration and document coverage, frequency, retention and recovery tests are defined in the institutional technical plan.
Application and schema upgrades must suit the installed version and institutional workflows. Testing, acceptance and rollback arrangements are defined with IT before rollout.
Centers and users, core workflows, capacity and concurrency, networking, integrations, migration mappings, backups and acceptance criteria.
Let’s talk about your center ↙Let’s talk about your center
Tell us about your needs, request a demonstration or ask a question. You can also call our team.
021 2842 8383 90006010 90007020Support and services office
North 2nd floor, No. 13, Alley 4, Zanjani St. (Kooy Parvaneh), opposite Tarbiat Modares University, Jalal Al Ahmad St., Tehran, Iran. Postal code: 1439916411Engineering office: Ilam Science and Technology Park, Zist Dadeh Pardaz Arka (BioArc)
