Subjective
Walking and daily mobility are improving; stairs remain uncomfortable. No new injury, locking, giving way, fever, redness, or swelling reported. Patient continues the agreed exercises.
Clinical AI · Medical Copilot
ConnectX Clinical AI brings patient context into the consultation, builds documentation as the doctor and patient speak, and carries the care plan into follow-up and billing preparation. Medical Copilot gives the doctor a live workspace for the work of the visit.

Live visit · Select a source or ask Copilot
Interactive example · Fictional patient
Interactive design example using sample data. Explore each stage at your own pace.
Understand the workflowBring the reason for the visit, relevant history, previous encounters, medications, and available records together before the consultation begins. The doctor starts with the context needed to ask a more informed next question.
Unified Memory connects the appointment call, WhatsApp conversation, clinical record, and follow-up around the patient. Authorized agents contribute to the same profile, so the next part of the care journey can build on what is already known.
The booking agent has the context for patient access. Medical Copilot and the doctor’s Medical Chat have the relevant clinical context for the work of care. Role and workflow permissions govern access to sensitive information.
Medical Copilot listens to the doctor and patient live. It combines their conversation with the patient’s existing context and develops the documentation while the appointment is still happening.
The patient profile and relevant history stay visible alongside the encounter.
The doctor’s and patient’s words appear as a continuing, speaker-labelled conversation.
The central workspace fills with subjective history, objective findings, observations, flags, medication checks, and the developing plan. The doctor can follow a section back to the relevant conversation and review it as it takes shape.
The doctor can discuss a developing section, ask about the patient’s context, or pose a clinical question in the same workspace. Medical Copilot responds while the live conversation and documentation continue.
Council Mode brings together AI specialist perspectives to help the doctor examine a question from more than one angle. The clinician weighs the reasoning and evidence and makes the clinical decision.
The documentation work begins with the conversation itself. The doctor reviews a structured draft while the details are fresh, instead of having to rebuild the encounter from memory afterwards.
Patient history, transcript, and developing sections are available together. That reduces the work of switching between sources and gives the doctor more room to listen, ask, and explain. The time saved depends on the specialty, encounter, and review workflow.
Medical Chat, available in the doctor’s account, can interpret MRI scan images, written radiology reports, and lab results alongside the patient’s history. The doctor can ask questions, discuss findings, and connect them to the wider clinical picture.
This is a clinical support workflow for the doctor. Image and record interpretation informs the clinician’s judgment; the AI caller handles patient access and coordination.
When the session ends, ConnectX generates structured documentation from the encounter and patient context, designed around Saudi medical documentation requirements.
The draft organizes the encounter into clinical sections, including subjective history, objective findings, assessment, and plan (SOAP).
The doctor checks the record, corrects or adds detail, and approves the documentation. The live transcript and clinical context stay close to that review so a draft can be assessed against what was actually discussed.
Clinical conversations can move between Arabic, English, medical terms, and the patient’s own description of a symptom. ConnectX supports that conversation as it becomes a structured clinical record.
Review language quality with the specialties and patient populations your team serves. Negation, medication instructions, timing, and the distinction between a reported symptom and an observed finding all matter to the final note.
The encounter also becomes a patient handout: medication instructions, the agreed care plan, and the next appointment or follow-up instruction in a format the patient can use.
The summary is ready for the team to review and send through WhatsApp. The patient receives a clear reference for what was discussed, while the care team keeps the handout connected to the encounter.
When the doctor gives a follow-up instruction during the consultation, ConnectX passes it to the appointment agent. The agent schedules its own outreach by call or WhatsApp to contact the patient and arrange the next visit.
The care plan continues beyond the note. Appointment reminders and automatic follow-up after a missed visit help bring an unfinished booking journey back to the team’s attention.
ConnectX prepares billing codes, supporting reasoning, and an Integrity Score from the clinical documentation. Its insurance agent draws on NPHIES knowledge, insurer policies, and Saudi requirements to help identify gaps before submission.
The billing team can review the proposed codes and the reasoning behind them, then address missing or inconsistent documentation. A higher Integrity Score indicates a higher estimated likelihood of acceptance; the payer makes the final decision.
The billing team reviews and submits the claim. ConnectX helps reduce avoidable rejections and the revenue loss that can follow incomplete or inconsistent claims.
Patient access, clinical documentation, and billing preparation are parts of the same care journey. ConnectX connects them through shared context and assigned responsibilities, so the next team receives the information needed for its part of the work.
Hospital and nursing workflows extend that support to bedside documentation, handovers, and team coordination, shaped around the care setting and the organization’s permissions.
Recovery carries clinician-defined programs into ongoing check-ins, reminders, and follow-up. Patient responses and connected wearable information can provide context between appointments.
The care team defines the program and the conditions that need attention. Agents support follow-through and route exceptions through the clinical escalation workflow.
Medical Hub supports authorized record sharing and collaboration around the patient. The relevant history, encounter, and follow-up context stay connected as care moves between people and teams.
Clinical access follows the organization’s roles and permissions, keeping collaboration tied to who needs the information for their work.
The doctor remains responsible for clinical decisions and approval of the documentation. The billing team reviews and submits claims. Follow-up agents act on the plan and responsibilities defined for their workflow.
ConnectX is hosted in Saudi Arabia. Explore how data protection, clinical access, and accountability support these workflows on the Trust page.
Ambient clinical documentation begins with the doctor-patient conversation. ConnectX Medical Copilot supports that work as a live AI medical scribe and consultation workspace: it develops a speaker-labelled transcript and structured clinical sections using the conversation and patient context. The doctor can ask questions as the visit continues and reviews the documentation before approval.
Yes. It listens to the doctor-patient conversation live and develops the transcript and clinical sections using the conversation and the patient’s existing context.
Yes. The doctor can discuss a section or ask a question in the Copilot workspace while live transcription and documentation continue. Council Mode adds AI specialist perspectives for the doctor to consider.
The doctor checks, edits, and approves the automatically generated documentation. ConnectX supports that review with the encounter transcript and patient context.
Yes. Medical Chat in the doctor’s account supports MRI images, written radiology reports, and lab results with patient context. Its interpretation supports the doctor’s clinical judgment.
Yes. A spoken instruction such as returning next week becomes a task for the appointment agent. It schedules outreach by call or WhatsApp to contact the patient and arrange the visit.
It estimates the likelihood of claim acceptance. A higher score indicates a higher estimated likelihood, not a payer commitment. The billing team reviews the codes, reasoning, and documentation before submitting the claim.
The aim is to reduce the work of drafting and reconstructing the encounter. The amount depends on the specialty and review process. Evaluate the complete workflow, including the time needed to check, correct, and approve the note. ConnectX has not published a measured reduction to date.
Yes. Medical Copilot supports Arabic and English conversations, including encounters that move between the two. Evaluate the resulting record with clinicians familiar with your specialty and patient population, including medication instructions, negation, and the distinction between symptoms and observed findings.
Follow one encounter from patient context to the approved note. Compare live assistance, transcript traceability, corrections, and the total time needed for clinician review. Then examine patient handouts, follow-up, billing preparation, and data handling. The consultation-to-note walkthrough shows the details to inspect; the Trust page supports the deployment discussion.
Bring your electronic health record (EHR), documentation templates, scheduling process, and billing requirements to a clinical demo. We will review the integration path and the responsibilities of each team. The doctor approves the documentation; the billing team reviews and submits the claim.
ConnectX prepares proposed billing codes with reasoning and an Integrity Score, drawing on NPHIES knowledge and relevant insurer and Saudi requirements. The billing example includes an illustrative ICD-10-AM diagnosis code for review. The score estimates acceptance likelihood; it does not determine the payer's decision.
Show us where your team spends time before, during, and after the appointment. We’ll explore the clinical workflow, the review process, and the systems that connect them.