Integrated Internal Operations Platform
Preliminary document of processes, modules, and functional scope for the digitalization, coordination, and automation of the internal operation of a patient-care organization.
1. InTouch overview
InTouch will be an internal digital platform designed to centralize and organize the operational patient journey, staff responsibilities, appointment coordination, transportation, internal processes by area, administrative follow-up, and preparation of insurance and internal billing workflows.
Objective
Transform manual processes, phone calls, notes, and spreadsheets into a centralized system where every department knows what to do, when to do it, and the current state of every process.
General operational flow
NEW PATIENT → INTERNAL REGISTRATION → CLASSIFICATION → APPOINTMENT → REMINDERS → TRANSPORTATION → PICKUP → ARRIVAL → CHECK-IN → INTERNAL PROCESS → SERVICES / AREAS → FOLLOW-UP → NEXT APPOINTMENT → RETURN TRANSPORT → OPERATIONAL CLOSURE → ADMINISTRATIVE REVIEW
2. Internal patient management
InTouch provides a central operational profile for each patient. It serves as the reference point to check status, tasks, appointments, transportation, and related activity.
- New patient registration and internal profile creation.
- Personal data, address, phone numbers, and authorized contacts.
- Emergency contact and related responsible parties.
- Photograph and internal documentation attached to the profile.
- Assigned branch, location, or center.
- Internal patient classification.
- Coordinator or responsible staff.
- Transportation needs and operational preferences on file.
- Administrative insurance classification.
- Patient status: active, pending, inactive, or other configurable states.
- Internal notes and follow-up by department.
- Activity history and operational timeline.
Patient Timeline
Every relevant event generates an entry in the patient's timeline to maintain full process traceability.
- Patient created or updated.
- Documentation added or flagged as pending.
- Appointment created, confirmed, rescheduled, or canceled.
- Transportation assigned.
- Patient picked up and delivered at destination.
- Check-in completed.
- Stage or internal area change.
- Process marked as completed.
- Follow-up or new appointment created.
- Patient returned home.
3. Appointments, calendars, reminders and messaging
The appointment system is InTouch's temporal coordination center. It organizes processes by patient, location, department, area, and responsible staff.
- Organization-wide calendar.
- Calendars per branch or location.
- Calendars per doctor, staff member, or department.
- Individual patient calendar.
- Configurable appointment and process types.
- Configurable duration and time windows.
- Recurring appointments and follow-up processes.
- Confirmation, rescheduling, cancellation, and no-show.
- Waiting list and pending processes.
- Internal messaging related to the appointment.
- Operational notifications and alerts.
Reminder automation
InTouch can execute automatic rules before and after each appointment. Rules are configurable based on operations.
- Pre-appointment reminder.
- Confirmation request or registration.
- Verification of required transportation.
- Alert when an appointment has not been confirmed.
- Task creation for the responsible secretary.
- Alert for unassigned transportation.
- Later follow-up when the process requires a next action.
4. Transportation, pickups and routes
Operational module to coordinate patient pickup, transfer, destination, and return based on scheduled appointments and needs.
- Driver registry and operational availability.
- Assignment of patients to drivers.
- Route creation and organization.
- Pickup and destination addresses.
- Internal or external destinations registered in the system.
- Patient sequence per route.
- Vehicle operational capacity when applicable.
- Estimated schedule control.
- Transportation status tracking.
- Recording of delays and incidents.
- Coordination of the patient's return trip.
Transportation states
- Pending.
- Assigned.
- En Route.
- Arrived at pickup point.
- Patient Picked Up.
- In Transit.
- Arrived at Destination.
- Waiting.
- Return Assigned.
- Returning Patient.
- Completed.
Route organization
The system assists with route organization using internal operational rules.
- Zone or location.
- ZIP code or geographic area.
- Appointment time.
- Destination.
- Driver availability.
- Vehicle capacity.
- Schedule compatibility across patients.
5. Patient Flow — internal patient journey
Once a patient arrives, InTouch lets you visualize and manage their journey across the organization's stages and internal areas.
Configurable flow (example)
ARRIVED → CHECK-IN → WAITING → AREA 1 → AREA 2 → SERVICE → FOLLOW-UP → CHECK-OUT → WAITING FOR TRANSPORT → RETURNING HOME
- Arrival time recording.
- Patient check-in.
- Stage or area assignment.
- Current owner of the process.
- Time spent in each stage.
- Movement between authorized areas.
- Wait-time alerts.
- Recording of completed processes.
- Checkout preparation.
- Handoff to the return-transport process.
Operational Flow Board
Authorized staff see a real-time board with the patient, current stage, time in stage, and owner. The system flags operational delays and generates alerts or follow-up tasks.
6. Follow-up and operational continuity
At the end of the day's process, InTouch reviews pending operational actions and helps coordinate patient continuity.
- Creation of the next appointment.
- Registration of pending follow-up.
- Administrative tasks.
- Pending documentation.
- Follow-up calls or contacts.
- Coordination of external processes as recorded administrative activity.
- Transportation needed for a next appointment.
- Responsible-department assignment.
- Due date and priority.
- Escalation of uncompleted processes.
PROCESS COMPLETED → PENDING DETECTION → TASK CREATION → OWNER ASSIGNMENT → FOLLOW-UP → VALIDATION → CLOSURE
7. Central internal tasks system
Task engine that turns events and pending processes into visible, assignable responsibilities.
- Manual or automatic task creation.
- Assignment by user, role, or department.
- Priority and due date.
- Work statuses.
- Comments and internal notes.
- Related documents.
- Relationship with patient, appointment, transport, or process.
- Change history.
- Automatic escalation by rule.
- Audit of creation, assignment, and closure.
Task statuses
- Pending.
- Assigned.
- In Progress.
- Blocked.
- Waiting.
- Completed.
- Escalated.
Automation examples
- Patient with no next appointment → task for appointment coordination.
- Pending document → task for Patient Intake.
- Route without driver → alert and task for Transportation.
- Unclosed process → task for the area owner.
- Overdue follow-up → escalation to the Manager.
8. Admin dashboard and Command Center
Central operational view for Owner, Admin, and other authorized roles. Shows the organization's state in real time.
- Scheduled patients.
- Patients who arrived.
- Patients currently in process.
- Completed patients.
- Waiting patients.
- Active transports.
- Active drivers.
- Pending routes.
- Delayed processes.
- Pending tasks.
- Critical tasks.
- Overdue follow-ups.
- Pending administrative processes.
Views and alerts
- View per location with its own indicators.
- View per department (Reception, Transportation, Patient Coordination, Operations, Accounting).
- Operational alerts for delays, critical tasks, ownerless processes, and unassigned transports.
9. Insurance and internal billing
Organizes the internal administrative process related to insurance classification, recorded services, and preparation of the billing workflow.
- Administrative classification of the patient's insurance.
- Organization by registered insurance type or plan.
- Internal classification by service provided.
- Recording of completed processes or services.
- Validation of required operational documentation.
- Internal review states.
- Accounting panel.
- Identification of pending information.
- Preparation of the record for billing review.
- Recording that the process was sent to or worked in an external system, when applicable.
- Administrative status tracking.
Proposed internal states
- Pending Documentation.
- Under Review.
- Ready for Billing.
- Billing Processed Externally.
- Pending Response.
- Completed.
10. Users, roles and specialized portals
InTouch uses role- and function-based access control. Each portal is designed around the user's responsibilities.
- Owner — Executive view, indicators, overall status.
- Admin — Configuration, users, control, and administration.
- Manager — Operations, teams, tasks, and follow-up.
- Accounting — Insurance, classification, and internal billing.
- Doctors — Agenda and authorized internal processes.
- Nurses — Assigned patients, stages, and tasks.
- Secretary 1 — Patient Intake, registration, and documents.
- Secretary 2 — Appointments, calendar, and confirmations.
- Secretary 3 — Follow-Up, pending items, and operational continuity.
- Drivers — Routes, pickups, destinations, and returns.
11. Cerebro InTouch, agents and MCP
Internal automation layer made up of an operational orchestrator, specialized agents, and controlled MCP tools.
CEREBRO → SPECIALIZED AGENT → MCP REQUEST → PERMISSION VALIDATION → BUSINESS RULES → EXECUTION → AUDIT → PROCESS UPDATE
Cerebro InTouch
Orchestrator of events and processes. Analyzes operational state and determines which agent or process should intervene.
Specialized agents
- Patient Intake Agent.
- Appointment Agent.
- Transportation Agent.
- Patient Flow Agent.
- Task Agent.
- Follow-Up Agent.
- Operations Agent.
- Accounting Workflow Agent.
MCP — controlled tools
- create_patient / update_patient
- create_appointment / reschedule_appointment
- assign_driver / create_route / update_transport_status
- patient_check_in / move_patient_stage
- create_task / assign_task / escalate_task
- create_follow_up
- mark_service_complete
- prepare_internal_billing_record
12. Audit and internal traceability
The platform keeps traceability of relevant actions performed by users, departments, and authorized automations.
- User or agent that performed the action.
- Date and time.
- Affected module.
- Related process.
- Executed action.
- Previous and new state when applicable.
- Assignments and reassignments.
- Task creation and closure.
- Changes in appointments and transportation.
- MCP tool executions.
- Operational errors and exceptions.
13. Initial functional scope
- Centralization of the patient process.
- Appointment and calendar coordination.
- Operational reminders and notifications.
- Transportation and route management.
- Control of the internal patient journey.
- Follow-up and operational continuity.
- Task engine per department.
- Dashboards and Command Center.
- Administrative insurance classification.
- Internal billing workflow.
- Portals per role and responsibility.
- Internal automation via Cerebro, agents, and MCP.
- Audit and traceability.
14. Capabilities out of initial scope
- Direct electronic transmission of claims to insurance companies.
- Direct integration with clearinghouses.
- Automated exchange of clinical information with third parties.
- E-prescribing or electronic prescription transmission.
- Direct integrations with pharmacies.
- Direct integrations with labs or external providers.
- Automatically generated medical diagnosis.
- Autonomous medical recommendations.
- Clinical decision-making by AI.
- Any external integration not defined and approved within the corresponding scope.
15. Expected result
InTouch becomes the digital center of internal operations: a platform where every patient has a visible journey, every process has a state, every responsibility has an owner, every department has a portal tailored to its function, and every automation runs on rules, permissions, and audit.