PATIENT RECORDS / RAKT
Find the patient.
Review their history.
Find a patient’s visits, clinical notes, and investigation requests through the same patient record. Each consultation or admission has its own record, so staff can tell previous care from the current visit.
Explore the detailIDENTITY + ENCOUNTER + NEXT ACTION
Find the patient
and their previous visits.
- 01Registration
Recognise the patient and open the current visit.
- 02Consultation
Record the encounter and the next clinical tasks.
- 03Investigation & prescription
Follow the request into the relevant workflow.
- 04Return visit
Keep earlier context distinct from the new encounter.
Identify new and returning patients
A name alone is a poor way to recognise a returning patient. RAKT maintains a patient record with a unique hospital identifier within the organisation, contact and demographic information, and links to the work recorded around that patient. The organisation boundary matters: a shared application does not mean every organisation shares its patient list.
During a walkthrough, test the situations your reception team meets: similar names, an updated phone number, a returning patient, and information that is missing at registration. Agree who can correct demographic details and how the team should search before creating another record.
Keep a separate record for each visit
The patient record identifies the person. A visit or admission record, also called an encounter, describes their care on a particular occasion. Outpatient consultations, inpatient admissions, diagnostic requests, and emergency visits each carry information that belongs to that episode.
Keep this distinction in the demonstration. Open a returning patient, inspect the earlier visit, create a new encounter, and follow the current investigation request. Ask which information is carried forward and which must be recorded again. Clinical decisions and documentation remain the responsibility of the treating team.
Follow requests into the next department
Follow an outpatient investigation request to the lab or radiology team, and a prescription to the pharmacy. For an admission, check the ward and discharge records too. Use the same patient throughout the demonstration.
Try the outpatient patient journey and the laboratory release example. Look for the identifier that connects the records, the status that tells the next team what to do, and the person responsible for the next action. Check that the next team can find the result when they need it.
Review patient access and consent
RAKT includes organisation and department access controls, patient consent records, and encrypted identity fields in its data model. Each control has a different purpose. Access determines who can work with records; consent records support the relevant communication or processing workflow; field encryption protects selected stored values.
Review these with your administrators before importing patient data. Do not treat a product feature as a substitute for your organisation’s privacy, retention, or clinical governance decisions. The security page explains the controls and points to the applicable policy documents.
What to bring to the demonstration
Bring a blank registration form, a sample consultation format, and a de-identified example of a returning patient’s journey. Include one exception: a correction, an incomplete record, or a diagnostic result from a previous visit.
Ask reception, a clinician, and a diagnostic team member to follow the same example. Record whether each person can find the context they need and whether their access is appropriate. This reveals more than testing each module separately with a different patient.
COMMON QUESTIONS
Questions about this topic.
Is this the same as an EMR?
Patient records and clinical documentation are part of an EMR workflow. RAKT also includes operational department workflows, billing, and inventory; the HMS-versus-EMR guide explains the distinction.
Does one identifier mean data is shared across unrelated hospitals?
No. The patient identifier is scoped to the organisation. Access and organisation configuration must be reviewed for the intended deployment.
Can you import our old patient records automatically?
Migration depends on the source data, permissions, mappings, and agreed scope. Use the migration guide to prepare a sample and discuss what can be transferred.
PLAN A DEMONSTRATION
See how RAKT handles
your team’s work.
Use fictional examples or blank formats. Keep patient information out of an initial enquiry.