One continuous journey
for better care.

Share your center type, departments, approximate user numbers and current admission-to-treatment workflow. A demonstration can then focus on relevant scenarios and define the proposed scope.

The agreed scope can cover one unit or multiple centers. Rollout order, connections between units and future expansion are defined in the implementation plan.

Modules, center and user structure, custom forms, integrations and hosting affect the estimate. Setup, customization and maintenance are specified in the proposal and contract.

Timing depends on project scope, infrastructure readiness, customization and access to required services. Deployment, training, scenario testing and launch dates are agreed before implementation.

Dedicated deployment on the institution’s infrastructure is available. Server, network, domain, technical access and infrastructure maintenance responsibilities are reviewed and agreed in advance.

Web capabilities are accessible through a browser. Peripheral devices or local integrations may require configuration or a supporting tool, identified during technical assessment.

The technical teams review available services, data and permissions. Integration, mapping and exchange tests are scoped per center; a module does not imply a ready connection to every external system.

The structure, quality, identifiers, documents and volume of available data are assessed first. Migration scope, field mapping and verification must be agreed.

The center’s data ownership and export process should be explicit in its contract. Format, scope, timing and end-of-contract transfer arrangements are agreed for that institution.

Independent accounts and roles are aligned with responsibilities. Access for physicians, assistants, nurses, reception and administrators, as well as support access and confidentiality commitments, are agreed for the center.

Infrastructure, backup creation and retention, storage location and recovery responsibilities must be clear for the hosting model. Backup frequency and recovery tests are specified in the technical plan and contract.

Admission establishes the visit, physician and department. The physician can review history, examination, prescriptions and records in connected workspaces; the detailed workflow depends on center configuration.

For supported imaging requests, select a body region visually and specify details such as side and view. Favorites and list search are available alongside this workflow.

Forms and follow-up workflows can be designed with the center’s scientific team. Structured fields, checklists, questionnaires and research outputs are defined within the agreed customization scope.

BioArc supports independent accounts and roles. Viewing, recording, completion and supervision permissions are configured to match the institution’s teaching and clinical structure.

BioVisit provides patient booking and online services. Schedules, capacity, video, voice, text and document sharing can be included according to the agreed scope.

Training is planned by role. On-site or online delivery, content and sessions are agreed in the deployment plan. Training videos are also available in the learning section.

Use the chat button or call +98 21 2842 8383. Request logging, prioritization, issue resolution and development requests are defined at launch; response targets depend on the center’s contract.

Modules, forms, roles and integrations depend on each center’s needs and configuration. The demonstration reviews selected capabilities, prerequisites and customization so delivery scope is clear.

BioArc’s foundation uses open-source technologies. The listed open-source components do not require a separate commercial operating-system, web-server or database license.