Docs & Guides

Everything Your Team Needs to Learn the Product

The documentation covers every Care18 module in the same structure: what the screen does, who uses it, how it connects to other departments, and how administrators configure it. Release notes track what changed, while the API reference supports your integration team during setup and beyond.

  • Module guides
  • Admin & configuration
  • Roles & permissions
  • Release notes & API
Product documentation shown alongside a hospital dashboard
About the Docs

What You Will Find in the Documentation

Documentation is where a rollout either gathers pace or stalls. Care18's docs are organised so that a nurse, a billing coordinator and an IT administrator can each find their own path without wading through pages written for someone else. Every module guide follows the same pattern — purpose, day-to-day workflow, screens, and related reports — so once you have read one, the rest are predictable. Configuration pages sit alongside, covering roles, numbering, templates and integrations in the language your implementation team already uses.

  • Module guides covering purpose, workflow, screens and reports
  • Administration pages for configuration, numbering, templates and integrations
  • Roles and permissions documented by capability, not by guesswork
  • Release notes describing what changed in each update
  • API reference for integration and interface teams
Staff reading product documentation on a workstation

Key Benefits

  • Faster Onboarding for New Staff

    A new joiner can read the guide for their role and reach productive work without pulling experienced colleagues away from their shift.

  • Fewer Support Round-Trips

    Clear, task-shaped pages answer the common questions before they become tickets, so teams stay focused on rollout work instead of waiting on replies.

  • Confident Configuration Decisions

    Administrators can check what a setting actually controls and what it affects elsewhere before changing anything in a live environment.

  • A Shared Reference During Rollout

    Implementation leads, department champions and the Care18 team can all point to the same page when discussing how something should be set up.

Core Features

Key Features

  • Module Guides

    Each module gets a consistent walkthrough: purpose, who uses it, the daily workflow, key screens and the reports it produces.

  • Administration & Configuration

    Step-by-step pages for setup: organisation structure, numbering, charge lists, templates, notifications and integration settings, each with the effects spelled out.

  • Roles & Permissions Reference

    A capability-by-capability view of what each role can see and do, helping administrators assign access deliberately instead of experimenting live.

  • Release Notes

    A chronological record of changes, improvements and fixes, so teams can see what is new and prepare users for changed screens.

  • API Reference

    Endpoints, authentication, payloads and example requests for integration teams connecting analyzers, payment gateways or external patient channels to the platform.

  • Troubleshooting & FAQ

    Common issues grouped by module, with the checks to run first and the information to have ready when you contact support.

How teams use the docs

How the Documentation Supports a Rollout

The same pages serve configuration, training and day-to-day questions — at different moments.

  1. 01

    Configure With Reference

    Implementation leads follow the administration pages while setting up structure, numbering, charge lists and roles in the test environment.

  2. 02

    Build Training Material

    Department champions adapt module guides into session notes, so training reflects exactly how the system is configured for your hospital.

  3. 03

    Answer Floor Questions Fast

    During go-live, staff look up a screen or permission question themselves instead of waiting, keeping the ward and front desk moving.

  4. 04

    Track What Changed

    Release notes tell administrators which updates landed, what moved on screen and whether any configuration step is needed afterwards for their team.

  5. 05

    Extend With the API

    Integration teams use the API reference to connect lab analysers, payment gateways and patient channels once core workflows are stable.

Security & Compliance

Security Built Into Every Layer

Hospital data deserves enterprise-grade protection. Care18 is designed with security at its core — access control, encryption, auditability and recoverability.

  • Role-Based Access Control

    Every user sees only what their role permits, down to the field and report.

  • Encrypted Data

    Encryption in transit and at rest for records, attachments and backups.

  • Audit Trails

    Immutable, timestamped logs of who changed what, when and from where.

  • Secure Authentication

    Password policy, multi-factor options and session control for sensitive actions.

  • Cloud Backups

    Automated, encrypted backup schedules with retention policies you control.

  • Disaster Recovery

    Documented recovery procedures, standby infrastructure and restore testing.

Use Cases

Who Benefits

  • New Administrator Onboarding

    A freshly assigned administrator works through the configuration pages and permissions reference before making changes in production.

  • Training Session Preparation

    Trainers pull screens, workflows and permission notes from module guides to build role-specific sessions without starting from scratch.

  • Planning an Integration

    Developers read the API reference and troubleshooting pages first, so expectations are set before any interface work begins.

  • Evaluating an Update

    Before upgrading, administrators check release notes to understand what changed and to brief the departments affected in advance.

FAQs

Frequently Asked Questions

Module guides for every part of Care18, administration and configuration pages, a roles and permissions reference, chronological release notes and a full API reference, plus troubleshooting notes grouped by module for day-to-day questions.

Documentation Is Better With a Walkthrough

Book a demo and we will show the modules you care about, then point you to the exact documentation pages your team will use first.