CareSync documentation, ready when you need it.

What CareSync covers

CareSync combines hospital administration, patient care, diagnostics, pharmacy, finance, operational services, documents, reporting, automation and SaaS account controls in one role-aware system. What each person sees depends on the hospital, branch and permissions assigned to that user.

Best way to learn

• Start with Free Trial & First Login.
• Complete hospital structure before entering real patients.
• Create users and roles before testing clinical or financial work.
• Test one complete patient journey from registration to billing.
• Use the topic index on this page whenever a screen or workflow is unclear.

Important

CareSync documentation explains software operation. It does not replace your hospital clinical policy, legal requirements, privacy policy, financial controls or independent security review.

What the trial does

Start Free Trial opens the secure CareSync application directly. Trial provisioning, tenant creation, account security and onboarding stay inside the hospital software, so validation or provisioning errors remain visible on the trial form instead of being redirected into the marketing website.

Recommended flow

• Open Start Free Trial.
• Enter the hospital and owner details requested by the secure form.
• Complete email verification when OTP verification is enabled.
• Sign in as the Hospital Administrator.
• Complete the setup sequence using fictional or approved test data.
• Before trial expiry, review Account Billing and select the appropriate renewal path.

After the trial

Trial expiry does not immediately delete hospital data. Access follows the configured reminder, grace, renewal, suspension and retention policy. Renew from the secure account billing area when you decide to continue.

Included trial capacity

• 1 hospital and 1 active branch
• 5 active users
• 100 patients
• 150 appointments
• 100 OPD/IPD encounters
• 100 invoices
• 75 pharmacy transactions
• 50 combined lab/radiology orders
• 50 MB total document storage and 5 MB per file
• 10 external test messages
• 250 API requests per UTC day
• 1 successfully completed data export

What does not reset

Patients, appointments, encounters, invoices, pharmacy transactions, diagnostic orders, external messages and completed exports are cumulative for the full trial. Cancelling, archiving or deleting a record does not return cumulative quota.

What can free capacity

Deactivating a staff user can free an active-user slot. Permanently deleting a protected file version can release storage; soft-deleted or retained versions continue to count. The API counter alone resets at UTC midnight.

Limit or trial expiry

Existing information remains safe and readable. A reached resource limit blocks only the new operation for that resource. After trial expiry, the workspace becomes read-only while billing, support and permitted data export remain available. A successful paid activation removes trial-only limits immediately.

First login checklist

• Confirm you are inside the correct hospital workspace.
• Complete the onboarding or setup prompts shown to the administrator.
• Review hospital name, branch and department structure.
• Create only the minimum users required for testing.
• Confirm dashboard, patient, appointment and billing menus match the assigned role.

If something looks missing

CareSync hides modules that the signed-in role cannot use. Check the assigned roles and permissions before assuming a module is broken.

Implemented hospital workflows

• Platform hospitals, trials and subscription state
• Branches and departments
• Users, custom roles and permissions
• Patient registration and UHID
• Appointments, OPD and EMR encounters
• IPD, wards, rooms, beds, admission and discharge
• Nursing notes and medication administration
• Emergency and triage
• Operation Theatre and surgeries
• Laboratory and radiology workflows
• Pharmacy medicines and batch stock
• Inventory and suppliers
• Billing, invoices and payments
• Insurance / TPA
• Blood bank inventory
• HR employee register
• Ambulance, housekeeping and diet operations
• Assets, equipment and maintenance
• Secure document management and consent registry
• Audit trail, dashboards, reports and data export

Foundations that should not be treated as full UI workflows

• Attendance and payroll run foundations
• Purchase order foundations
• Pharmacy sales foundations
• Notification data foundations
• Subscription history and API client foundations
• Document metadata/version foundations
• ABDM/ABHA integration boundary

Why this distinction matters

Documentation on this page focuses on workflows that the uploaded CareSync project actually exposes. Foundation-only areas should be expanded and tested before being marketed as complete end-user modules.

Navigation

Menu groups are role-aware. A receptionist, doctor, nurse, pharmacy user, accounts user and Hospital Administrator can see different navigation even inside the same hospital.

Global patient search

• Search patients by supported identifiers such as name, UHID or phone.
• Depending on permission, search can also surface appointments, invoices, admissions, beds, medicines, laboratory orders, radiology orders, documents, staff, modules and guides.
• Use quick actions such as Create Patient, Book Appointment, Create Invoice, Admit Patient, Available Beds or Reports when offered.
• Confirm the patient/record before opening a clinical or financial workflow.
• Search results remain permission-filtered and scoped to the signed-in hospital context.

Lists and filters

CareSync list screens use search, filters and pagination. If a record appears missing, first check branch, date, status and active filters before creating a duplicate.

Recommended order

• Hospital profile and legal identity
• Branches
• Departments
• Wards, rooms and beds when IPD is used
• Users and roles
• Billing and tax settings
• Laboratory, pharmacy and operational masters
• Workflow validation with fictional records

Before production

Do not start real hospital operations until core masters, staff access and a full test journey have been validated.

What belongs here

• Hospital or organisation name
• Approved legal or billing identity fields available in your build
• Operational contact information
• Settings used by the hospital workspace

Good practice

Keep organisation details accurate before invoices, exports or formal reports are generated. Do not put developer credentials or secrets into public-facing profile fields.

When to use branches

Use branches when one CareSync hospital workspace operates more than one physical or operational location and the workflow needs branch context.

Setup steps

• Create the branch from Administration.
• Use a clear, unique branch name.
• Assign users to the correct branch context where applicable.
• Check branch filters in dashboards, lists and reports.

Avoid

Do not create a new hospital tenant merely to represent a branch unless your commercial and data-isolation design specifically requires separate tenants.

Examples

• OPD / clinical departments
• Laboratory
• Radiology
• Pharmacy
• Emergency
• Operation Theatre
• Accounts or administration where represented in the build

Setup tip

Use department names staff already understand. Avoid near-duplicate masters such as “Radiology”, “Radio”, and “Imaging” unless they are genuinely separate departments.

Structure

A bed belongs to the configured inpatient structure. Create wards first, then rooms, then beds according to how your hospital actually allocates inpatient capacity.

Daily control

• Use only available beds for new admissions.
• Use the transfer workflow instead of manually recreating an admission.
• Confirm bed status after transfer and discharge.
• Reconcile system occupancy with physical occupancy.

Create a user

• Use a unique staff email/login.
• Add the staff identity details required by your organisation.
• Assign only approved roles.
• Test the account before handing it to the user.

When staff changes

• Change roles when job responsibilities change.
• Deactivate access when the person no longer requires the system.
• Do not reuse one shared account for multiple staff members.

How it works

A user is one person. A role is a set of permissions. CareSync checks permissions on protected routes, so hiding a menu is not the only access control.

Recommended process

• Start from a real job responsibility.
• Grant the minimum permission set required.
• Assign the role to test users.
• Sign in as that user and verify allowed and blocked actions.
• Review access after staffing or process changes.

Example

An accounts user may need patient viewing, billing, payment and reporting permissions but should not receive clinical editing permissions unless the job genuinely requires them.

Purpose

The employee register stores workforce records. A CareSync user account is still the login identity, so an employee record and a login should not be treated as the same thing.

Good practice

• Keep employee identity accurate.
• Create a login only when the employee needs software access.
• Control access through roles and permissions.
• Deactivate login access independently when required.

Before creating

Search first. Duplicate patient records can split clinical and financial history.

Registration flow

• Search for the patient by supported identifiers.
• Enter required identity and contact details.
• Save the record and note the generated UHID where applicable.
• Continue to appointment, OPD, IPD or another permitted workflow.

Data quality

Use the hospital’s approved registration policy for names, dates, contact numbers and other identifiers. Correct the existing patient when appropriate instead of creating a second record.

Use search before action

• Find the patient before consultation.
• Confirm patient before admission.
• Confirm patient before laboratory or radiology orders.
• Confirm patient before pharmacy dispensing or billing.

Why context matters

CareSync keeps hospital workflows tied to patient and encounter context. Always confirm you are working on the intended patient before saving clinical or financial data.

Create an appointment

• Select the patient.
• Select the doctor or relevant service.
• Choose the available date and time.
• Save the appointment.
• Update the appointment status as the visit progresses.

When the patient arrives

Continue through check-in or queue workflow rather than creating a second appointment for the same visit.

Typical states

• Waiting
• Called
• Consulting
• Completed
• Cancelled where required

Daily flow

• Register or find the patient.
• Use the appointment or walk-in process.
• Place the patient in the active queue.
• Doctor opens the authorised patient context.
• Complete the visit after consultation and downstream work.

Cancellation

Use the provided status/cancellation workflow so the event remains auditable instead of deleting history.

Start correctly

Open the correct patient and create or open the relevant clinical encounter before entering consultation information.

During consultation

• Review patient context.
• Record authorised clinical notes.
• Add vitals when measured.
• Record diagnosis according to hospital policy.
• Add prescriptions and investigation orders as required.

Clinical responsibility

CareSync records information; it does not replace professional clinical judgement or your hospital approval process.

Vitals

Add measured vitals only to the correct patient encounter. Verify units and values before saving.

Notes and diagnosis

• Use clear clinical notes appropriate to the signed-in role.
• Record diagnosis only when authorised.
• Do not copy one patient’s text into another patient record.
• Correct errors using the workflow available to your authorised role rather than hiding history.

Doctor workflow

• Open the correct encounter.
• Add the prescribed medicine and instructions using available fields.
• Review before saving.
• Send the patient through the hospital’s pharmacy or follow-up process as required.

Important

Prescription entry and dispensing are separate responsibilities. Pharmacy stock should change only through the authorised dispensing workflow.

Admission flow

• Open IPD and choose Admit Patient. A direct /ipd/admit link opens the same admission workspace.
• Select the real patient and enter the admission reason.
• Choose an active Doctor user for the same hospital/branch when one is assigned.
• Choose an Available bed from a valid Ward → Room → Bed hierarchy.
• Submit once; CareSync rechecks and locks the bed before the admission is committed.
• Continue nursing, investigations, pharmacy, transfer and discharge from the active admission.

If a dependency is missing

• Use + New Patient when the patient is not registered.
• Use the Doctor/User setup action when the Doctor list is empty.
• Use Create Bed / Bed Master when the physical bed hierarchy is missing.
• After Create & Return, verify the new record is selected before submitting.

Safe failure behaviour

CareSync must not leave a half-created admission or occupied bed if a mandatory admission step fails. Validation problems return to the admission workflow with a corrective message. Unexpected system failures keep an Error ID for administrator diagnosis.

Transfer flow

• Open the active admission.
• Choose the destination ward/room/bed.
• Confirm the destination is available.
• Use the transfer action.
• Verify old and new bed statuses after the move.

Do not

Do not discharge and re-admit the patient just to change beds unless hospital policy genuinely requires a new admission.

Daily use

• Open the active inpatient admission.
• Choose the appropriate note type available in the screen.
• Record the nursing note clearly.
• Save under the authorised nursing user.

Patient safety

Confirm the patient and admission before saving. Nursing documentation should reflect the actual care delivered and your hospital policy.

Workflow

• Open Nursing for the active admission.
• Review the scheduled medication entry.
• Verify patient, medicine and instruction.
• Administer according to hospital clinical policy.
• Mark as administered only after the actual action is completed.

Separation of duties

Prescription, pharmacy dispensing and nursing administration are related but separate steps. Do not use administration status as a substitute for pharmacy stock movement.

Before discharge

• Confirm the patient is ready under hospital policy.
• Review pending clinical work.
• Review billing and payment status where required.
• Complete discharge-related notes or summaries available in your build.
• Use the IPD discharge action.

After discharge

Verify the bed becomes available when appropriate and that the admission remains in history rather than being deleted.

Create the case

• Select the correct patient.
• Record triage level and chief complaint.
• Record arrival time and other available case details.
• Keep the case status current as care progresses.

Possible outcomes

• Observation or ongoing emergency care
• Admission
• Discharge
• Referral or another status available in the configured workflow

Create the theatre record

• Select the correct patient and procedure.
• Link the admission when applicable.
• Select the responsible surgeon or available provider field.
• Set the scheduled start time.
• Update status as the case moves from scheduled to in progress, completed or cancelled.

Important

Use the OT record to coordinate software state. Clinical theatre checklists and surgical safety policy remain hospital responsibilities.

Typical order journey

• Order created
• Sample collected
• Processing
• Result entered
• Verified
• Final

Staff workflow

• Open the correct patient order.
• Confirm test and patient context.
• Update sample/processing state as work progresses.
• Enter results using authorised access.
• Verify/finalise according to hospital laboratory policy.

Critical results

Critical result escalation must follow your hospital’s authorised clinical process. Software status alone is not the escalation policy.

Workflow

• Open the patient radiology order.
• Confirm modality and scheduling information available in the record.
• Update work status as the study progresses.
• Enter or attach the authorised report using the available workflow.
• Verify completion state.

Scope note

Do not assume PACS or another third-party imaging integration exists unless it has been separately configured and verified for the deployment.

Use

• Maintain the blood bank record fields provided by the module.
• Keep availability/status current.
• Use role-based access for updates.
• Reconcile software inventory with the hospital’s controlled physical process.

Clinical control

Blood issue, compatibility, storage and transfusion safety must follow authorised blood bank and clinical policy.

Maintain stock

• Create or maintain medicine masters.
• Add stock to the correct batch.
• Keep expiry date and available quantity accurate.
• Review low stock and expiry information as part of physical reconciliation.

Dispense

• Open the correct patient/prescription context.
• Verify medicine and quantity.
• Use the authorised dispense action.
• Confirm the resulting stock movement.

Do not

Do not edit quantities simply to make the screen match. Investigate and reconcile stock differences using authorised inventory controls.

Daily use

• Maintain item masters consistently.
• Maintain supplier records where required.
• Record stock activity through the available module workflow.
• Monitor quantity and reorder needs using the information available in the system.

Scope

Purchase order foundations exist in the database, but they should not be treated as a complete procurement UI unless your deployment has explicitly implemented and tested that workflow.

What to record

• Asset/equipment identity
• Location or organisational context available in the screen
• Status
• Maintenance-related information supported by the module

Good practice

Use consistent asset naming and do not store secret credentials in asset notes. Physical maintenance sign-off still follows your organisation’s process.

Create an invoice

• Open Billing → Create Invoice, or start from a patient context.
• Choose the patient; use + New Patient if registration is not complete.
• Enter the first charge line, then use + Add another line only when another service is required.
• For every line choose Type, description, quantity, unit price, discount and tax. Newly added Type dropdowns remain fully searchable.
• Review the per-line total and invoice subtotal, discount, tax and estimated total.
• Submit once; the server recalculates and verifies the financial total before issuing the invoice.

Responsive invoice drawer

The invoice builder wraps fields on smaller screens instead of requiring sideways scrolling. If the patient is created from the invoice, return to the same invoice and verify the selected patient and entered lines before submitting.

Corrections

Use the provided cancel/refund/adjustment controls that apply to your deployment. Do not delete completed financial history to hide an error.

Payment flow

• Open the correct invoice.
• Confirm amount and permitted payment method.
• Record the payment.
• Verify the updated outstanding balance.
• Include the payment in daily reconciliation.

Reconciliation

Compare collections with posted invoices and payments. Investigate differences rather than creating duplicate receipts.

Use carefully

• Select the correct patient/claim context when available.
• Maintain payer/TPA information using the supported fields.
• Keep claim status current.
• Reconcile financial outcomes with hospital billing.

Scope

Insurance rules vary by payer and contract. CareSync records do not replace insurer authorisation, legal documentation or hospital claims policy.

What Account Billing shows

• Current plan and billing cycle
• Trial or subscription period dates
• Current amount based on server-side pricing
• Usage information such as users, branches, documents or storage where configured
• Invoices and payment history
• Auto-renew/cancellation controls supported by the application

Renewal flow

• Review expiry reminders.
• Open Account Billing before access becomes restricted.
• Choose the plan/billing cycle offered by the secure application.
• Complete the configured payment process.
• Wait for verified payment activation rather than refreshing or creating duplicate payments.

Important

Public website prices are informational. The secure CareSync application recalculates payable price and tax server-side before payment.

Use

Use the ambulance module for the operational fields exposed by your CareSync build and keep records tied to the correct hospital context.

Operational control

Dispatch safety, driver validation, emergency communications and transport policy remain organisation responsibilities outside the software record itself.

Daily use

• Use clear location/task context.
• Update the task or status when work changes.
• Keep completed activity traceable instead of deleting history.

Use with local SOPs

CareSync helps record operational work; cleaning standards, infection-control procedures and supervisor checks remain hospital policy.

Good practice

Confirm the patient/admission context and use only instructions authorised by your hospital’s clinical and dietetic process.

Important

Software entries are not a substitute for dietitian or clinician review when such review is required.

Upload flow

• Open Documents and choose Upload Document.
• Select the document type/category.
• Link the patient, consultation, admission, invoice, employee or another supported record when needed.
• Add title, document date, tags, expiry or retention information available in the screen.
• Upload an allowed file within the configured size limit.

After upload

• Use detail view to preview or download.
• Edit metadata when authorised.
• Upload a replacement version instead of losing previous history.
• Archive documents that should remain retained.

Security

Private document files are served through authorised routes, not predictable public URLs. Do not upload passwords, API secrets or unrelated confidential data.

Purpose

The consent registry gives the hospital a place to record supported consent metadata and status inside the patient/hospital context.

Important

Your legal team and clinical policy define what consent is required, how it is captured and how long it is retained. A database record alone does not prove legally valid consent.

Hospital user actions

• Open the notification badge/feed.
• Mark individual notifications read or unread.
• Use Mark All Read when appropriate.
• Archive or delete only when the available permission and workflow allow it.
• Update non-critical channel preferences where supported.

Unread count

The header notification badge reflects unread state. Opening or marking a notification read changes its status; the full Notification Center keeps notification history according to the application rules.

Platform broadcasts

Platform Super Admin can create governed broadcasts for approved audiences and channels. Recipient resolution happens server-side; arbitrary browser-supplied recipient IDs are not trusted.

Rule structure

• WHEN: choose a supported patient, appointment, clinical, IPD, nursing, lab, pharmacy, billing, insurance, inventory, workforce or schedule trigger.
• IF: optionally restrict the rule by field, operator and value.
• THEN: create a task, notification, follow-up, governed request, report or escalation.
• Governance: set branch scope, approval, retry, escalation, working hours or schedule options available in the screen.

Safe activation

• New rules start in test mode.
• Use Dry Run first.
• Review execution history.
• Sensitive actions enter the Approval Inbox.
• Activate only after the result is understood.

Reliability

Automation uses tenant-scoped execution, idempotency protection, bounded retries and logs. It does not silently perform destructive clinical or financial changes.

Dashboard

Dashboard values come from database records. A zero or empty state can be valid when no matching data exists.

Before reporting an issue

• Check branch filter.
• Check date range.
• Check user role/permissions.
• Check workflow status.
• Confirm demo or production data actually exists.

Reconciliation

• Reconcile collections with invoices and posted payments.
• Validate occupancy against active admissions and physical beds.
• Treat exported reports as sensitive files.

What audit is for

Audit logs support accountability by recording selected security-sensitive and operational actions with user and context information.

How to use

• Filter to the relevant time/user/action where available.
• Use audit evidence when investigating access or workflow changes.
• Do not alter application history to hide an error.
• Keep audit review restricted to authorised roles.

API client lifecycle

• Create a named client for one approved integration.
• Select only the scopes the integration requires.
• Copy the generated secret once and store it securely.
• Use the client ID and secret only from the approved server/application.
• Revoke the client when it is no longer required or the secret is exposed.

Security

Never place client secrets in frontend JavaScript, screenshots, public documentation or support messages. API access still respects the platform’s supported scope and tenant design.

Integration scope

CareSync includes integration boundaries and API clients. A named third-party integration should be advertised only after it has been separately built and verified.

Export behaviour

CareSync export jobs include tenant-scoped CSV records only from tables designed with hospital ownership. Export files are sensitive and should be downloaded only by authorised users.

Safe handover

• Request export from an authorised hospital account.
• Wait for the job to complete.
• Download within the configured expiry period.
• Store the ZIP securely.
• Handle private document binaries through an approved secure handover process.

Retention

Expiry, cancellation or suspension does not immediately delete clinical data. The real retention/deletion policy should be configured, published and legally reviewed.

OTP flow

• Enter the requested account email.
• Check the mailbox for the six-digit OTP when enabled.
• Enter it before expiry.
• Use resend only after the cooldown period.
• Never share an OTP with support staff.

If email does not arrive

• Check spam/junk.
• Confirm the email address was typed correctly.
• For a production deployment, verify the mail configuration and notification worker.
• If the issue remains, contact CareSync Support at support@caresync.in without sending passwords or patient data.

Login

• Use your own account.
• Do not share passwords.
• Repeated failures may trigger additional risk controls such as CAPTCHA.
• Sign out from shared devices.

Forgot password

Use the Forgot Password flow. Reset tokens are designed to expire and become unusable after successful reset. Support should never ask for your existing password.

CAPTCHA

Production CAPTCHA requires the configured provider and keys. Development bypass settings should never remain enabled in production.

Application controls represented in the project

• Role-based permissions
• Tenant/hospital context on protected data
• CSRF validation on ordinary POST actions
• Prepared database statements
• Rate-limited login
• Password reset token protections
• Audit logging for important operations
• Private document delivery
• Payment webhook signature verification boundary

Production operator responsibilities

• Use HTTPS.
• Use secure cookies and strong unique secrets.
• Use least-privilege database credentials.
• Protect private file storage.
• Monitor logs and failed jobs.
• Test backups and restores.
• Complete an independent security and privacy review before real hospital use.

Core rule

Hospital-owned queries use the authenticated hospital context. Normal hospital users should not be able to switch to another tenant merely by changing a URL or browser value.

Platform separation

Platform Super Admin has platform-only responsibilities and does not receive ordinary clinical navigation or a hospital tenant context.

Re-test after changes

Tenant isolation and RBAC should be re-tested after schema, controller or permission changes.

Step 1: Search documentation

Use the search box in this Documentation page. Search by screen name, module, action or problem such as “billing”, “notification”, “bed”, “OTP” or “renewal”. No page reload is required.

Step 2: Collect safe details

• Page or screen name
• Approximate date/time
• Signed-in role
• What you clicked
• What you expected
• What actually happened
• Error ID if CareSync displays one

Step 3: Email support

Send unresolved issues to support@caresync.in. Do not send passwords, OTPs, API secrets, payment secrets or unnecessary patient-sensitive information.

What the software supports

Authenticated customers can have a tenant-scoped Support area with ticket creation, replies, SLA due times and resolution history.

How to use it

• Search documentation first.
• Create a ticket only if the in-app Support area is enabled for your role/deployment.
• Include safe reproduction steps and Error ID.
• Reply inside the same ticket instead of creating duplicates.

Official external mailbox

For external support communication, use only support@caresync.in.

What it can do

The current assistant can use built-in CareSync guidance and supported allow-listed operational questions according to the signed-in role. External AI integration is optional.

Limits

• It does not accept arbitrary hospital IDs from the browser.
• It does not execute arbitrary SQL.
• It should not make silent clinical decisions.
• Clinical drafts require authorised human review.
• If an external AI provider is not configured, built-in guidance remains available.

A page or menu is missing

• Check the signed-in role.
• Check permissions.
• Check hospital/branch context.
• Confirm the module is part of the implemented workflow.

Dashboard is empty

• Check date range.
• Check branch.
• Check status filters.
• Confirm matching records actually exist.

A list record is missing

• Clear search/filter values.
• Check pagination.
• Check active/inactive status.
• Search by the correct patient or identifier.

Email/OTP not received

• Check spam.
• Confirm email spelling.
• Wait for resend cooldown.
• Production operator should verify mail configuration/worker.

Still unresolved

Email support@caresync.in with the screen name, time, role, safe reproduction steps and Error ID. Never send passwords or secrets.

Platform responsibilities

• Hospitals and trial state
• Subscriptions and pricing
• Payments
• Support oversight
• Automation health
• Content/documentation management
• Platform settings
• Exports and audit
• API clients
• Platform notifications

Separation

Platform Super Admin is not a hospital user and should not be used as a shortcut into patient care screens.

Platform actions

• Review hospital records.
• Review trial/subscription state.
• Extend trial only through authorised platform controls when appropriate.
• Change hospital status only with a clear operational reason.
• Use audit records when investigating lifecycle changes.

Do not

Do not delete hospital data merely because a trial or subscription ended. Retention and offboarding must follow the configured policy.

Pricing administration

• Review plan configuration.
• Update plan prices using authorised platform controls.
• Maintain tax configuration.
• Use coupons only when approved and supported.

Payment safety

PaymentService creates an invoice before checkout and verified provider webhook events are used for activation. Browser-submitted totals are not trusted.

Refunds

Refund processing is not automatically customer-facing in the current build. Provider-specific financial authorisation is required before enabling automated refunds.

Content

• Create and edit approved help/documentation content where the platform CMS is used.
• Archive obsolete content rather than leaving conflicting guidance active.
• Use safe screenshots with no patient data, passwords, tokens or API secrets.

Broadcasts

• Choose an approved audience.
• Preview resolved recipient count.
• Choose permitted channels.
• Send now or schedule.
• Review notification worker health for scheduled delivery.

Settings

Platform settings can hold supported values such as trial days, grace period, support identity, payment configuration and other lifecycle controls represented in the project.

Automation/worker health

• Review failed jobs.
• Review notification outbox failures.
• Confirm OS scheduler is actually configured in production.
• Use dry-run or controlled execution where available.
• Keep cron/application secrets private.

What to back up

• MySQL database
• Private uploaded documents in protected storage
• Relevant production configuration kept through your secure secrets process

Prove the backup

A backup is not proven until it has been restored into a separate test environment and checked.

Retention

Do not automatically purge clinical data simply because access is suspended. Publish and legally review the real retention and deletion policy, including legal holds and secure handover.