Pensieve Learn
Every role this site publishes a page for has a path here.
Pensieve Learn teaches the tasks a person performs. Each path runs in a Cornea rehearsal site modelled on your hospital’s own configuration, never on live patient records. What a trainer demonstrates, your staff can change afterwards without opening a ticket with us.
Each person’s interface in Pensieve is a projection of their permissions, so a staff nurse, a billing executive, and a quality officer each learn a smaller surface than the whole platform. That is why this program is organised by role first and by subject second.
The program has one measure. A hospital is trained when it stops asking us to change its own configuration. Forms are built in Glyph by the department that fills them. Sites, wards, tariffs, and roles are modelled in Cornea by your administrators. The apps no vendor ships are built in Durin, without code, on the same governed data. None of that is gated behind our services team, which is what makes independence reachable.
Learning paths
Paths, defined by what the person can do at the end
The roles below are the ones a hospital actually staffs, and each maps to exactly one path. A path is defined by the tasks a person must be able to perform at the end of it.
Clinicians
Consultant / Specialist, Surgeon, Resident / RMO, CMO / Medical Director
- Write, amend, and countersign a note in Atlas, and name the author, timestamp, and department on any line in front of them.
- Place one order in Forge, whether a drug, a test, a scan, a cross-consult, or a form, and follow it through fulfilment, billing, and result without leaving the record.
- Build their own department’s form in Glyph, start to finish.
- Explain, by pointing to the authorization check, why a colleague sees records they do not.
Nursing
Staff Nurse, Ward In-charge / Matron, Chief Nursing Officer
- Run a drug round from the Quest eMAR, recording each dose at the bedside as it is given.
- Hand a shift over on a structured Glyph form that the incoming nurse reads at the start of their shift.
- Acknowledge, escalate, or close a Sentinel alert, and show where that acknowledgement was written.
- Carry a Cadence care-plan checklist to its close.
Front office and admissions
Front-desk Executive
- Register a patient, admit through Gate, and assign a bed.
- State what an admission opens in the consent gate, and what closes when that admission ends.
- Book, move, and cancel an appointment, and send the reminder through Raven.
Pharmacy, laboratory, imaging, and stores
Pharmacist, Lab Technician, Radiographer, Procurement Manager
- Act on a Forge order at the bench and return the result to the clinician who placed it, without a phone call.
- Confirm in Westron that an analyser, modality, or archive is delivering into the record, and see the moment it stops.
- Track batch and expiry, and carry an indent through to GRN.
- Show consumption against the fulfilment that caused it.
Billing and payer
Billing Executive / Cashier, TPA / Insurance Coordinator, CFO / Finance Head
- Close a day on the Vault ledger: tariffs, deposits, splits, and settlements.
- Package a claim for the payer as NHCX-ready FHIR, straight from the record.
- Trace a denial back to the charge, and the charge back to the order that produced it.
- Show that a service delivered was a service billed, from the fulfilment record.
Quality, records, and infection control
Quality & Accreditation Head, Infection Control Officer, MRD Officer / HIM
- Map a NABH or JCI chapter in Vigil onto work the hospital already performs.
- Raise an incident and carry it through RCA to a closed CAPA.
- Pull chapter evidence out of the record the hospital keeps as it works.
- Read record completeness and ICD-11 coding as they stand today.
IT, biomedical, and administration
CIO / CTO / IT Head, Biomedical Engineer
- Install orophin, and explain to a network team what the egress rule they are approving lets out.
- Bring up a connection in Westron and read its health and message flow.
- Model a site in Cornea and rehearse a configuration change before it becomes real.
- Grant and revoke access in Cirith, and produce the audit record of having done so.
- Run PM and calibration as Quest schedules, and draw the FMS evidence from them.
Executive and oversight
CEO / Managing Director, Medical Superintendent
- Read a Falcon view and name the record each number is derived from.
- State which questions the platform can answer today and which it cannot.
- Ask for a new view without waiting on a vendor release.
Allied clinical
Dietician, Physiotherapist
- Route a diet order to the kitchen on the same path as any other order.
- Schedule a therapy plan in Quest and record a functional assessment in Glyph.
- Make sure a session that happened is a session that was charged.
How a path runs
The rehearsal site is your own configuration
The curriculum
Grouped by subject
A clinician placing an order never needs to know which tool the order passes through next, so the lessons follow the subject. Each subject names the part of the platform it sits on, and a path draws its lessons from several subjects.
Curriculum
The record
One clinical record, with provenance on every line. Atlas, Glyph, and the MRD view of both.
Writing a note that carries its provenance. Author, timestamp, department, and signature on every entry. What an amendment does to the original, and what a countersignature means.
Finding a history. How the record assembles across visits and departments, and how ICD-11 coding is applied as each entry is made.
Forms your department owns. Building a form in Glyph and putting it in front of the people who will fill it. Who is allowed to change a form, and where that change is recorded.
Completeness and deficiency. The MRD view: what an incomplete record looks like, who is asked to close it, and how retention is logged.
Curriculum
Authorization
Cirith, consent, the patient lens, and the audit trail. The part that decides what anyone can see.
Why your screen is smaller than your colleague’s. The interface is a projection of permissions, so each role learns a smaller surface. What that means when two people open the same patient.
Relationships, beyond roles alone. How Cirith decides access from the relationship between a person and a patient, and why a job title on its own does not grant a read.
Consent as an object. The two-plane model: the patient owns the data, and an admission opens a scoped path for the care team that closes when the admission ends.
Answering who saw this. Reading the audit trail. Every action is written in the same transaction as the change, and a query on the trail answers the question.
Curriculum
Orders and results
Forge, Quest, Sentinel, and Cadence. One order, placed once, carried to everyone who has to act on it.
Placing one order. A drug, a test, a scan, a cross-consult, or a form, all placed through the same object, and each one arriving with the charge already attached.
Fulfilment at the bench. Acting on the order in pharmacy, laboratory, or imaging, and sending the result back to the clinician who asked for it.
Schedules and due cards. Quest as the time layer: dose schedules and the eMAR, patient reminders, and equipment PM and calibration on the same mechanism.
Alerts and approvals. Each Sentinel alert goes to one named owner. Cadence carries the checklist, the approval, and the ticket to a close.
Curriculum
Billing
Vault, on the same record as the clinical work. Charge capture, the ledger, claims, and denials.
Charge capture at fulfilment. The charge comes off the same object as the service, so delivered is billed. Where a charge can still be missed, and how that shows up.
The ledger. Tariffs and rate cards, deposits, splits, and settlements, with GST worked out on each charge as it is raised.
Claims. Packaging a claim as NHCX-ready FHIR from the charges already in the record.
Denials. Working a denial back to the charge and the order behind it, and reading the pattern across denials in Falcon.
Curriculum
Accreditation evidence
Vigil and Falcon. Evidence as the exhaust of running on the platform, accumulated long before an audit is called.
Chapter mapping. Mapping NABH and JCI chapters onto work the hospital already does, so the evidence has a source before anyone asks for it.
Incident to CAPA. Raising an incident, running the RCA, opening the CAPA, and closing it with the record of what changed.
Producing evidence. Drawing chapter evidence from the governed record. What an auditor is shown, and what the audit trail adds to it.
Indicators. Reading a Falcon indicator and naming the underlying record it is derived from, so a number can be defended in a review.
Curriculum
Administration
Cornea, Westron, orophin, Cirith, Durin, and Raven. The parts your own administrators operate.
Modelling a site. Departments, wards, roles, tariffs, and forms modelled in Cornea and rehearsed on a dummy site before the configuration is real.
Access administration. Granting and revoking in Cirith: who may grant what, what the grant is scoped to, and the audit record the grant itself produces.
Connections. Bringing up a connection in Westron to a machine you already own, watching its health and message flow, and the outbound-only shape of the orophin bridge.
Building the long tail. Durin: staff building the apps no vendor ships, on the same governed data, without code and without a new access model.
Patient messaging. Configuring Raven for SMS, email, and WhatsApp, and knowing which messages leave the hospital and on whose authority.
The catalogue
The catalogue is open on Pensieve Learn.
The public catalogue at learn.pensievelabs.org lists every course, filterable by role and by tool, and the certifications each chain of courses leads to. Anyone can browse it. The lessons open after sign-in.
Assessment
What our certificate is, and what it is not
At the end of a path there is an assessment. It is worth being exact about what it means, because the word certification is used loosely in this industry and we would rather be the ones who narrow it.
- We set it and we mark itThe assessment is written by Pensieve and marked by Pensieve. It is not accredited by NABH, JCI, NMC, INC, or any external body.
- It confers nothing clinicalIt is no professional qualification, no licence, and no continuing-education credit. It says nothing about anyone’s ability to practice.
- It records one thingThat a named person completed a named path and performed the tasks in it, on a dated attempt, in a rehearsal site that holds no live records.
- The hospital holds the resultThe record of who has completed which path belongs to the hospital and can be exported. It is a competence register you own, and we hold no badge on your behalf.
The assessment is passed by doing the work. A person is asked to carry out the tasks listed on their path in the rehearsal site while someone watches: place the order, run the drug round, close the CAPA, package the claim. A written answer about a screen is no evidence that anyone can work it.
If a hospital needs an externally accredited qualification, this is not it, and we will say so in writing to your HR department.
On site, remote, and self-paced
Delivery. The fee is a contract matter. The cost that actually decides whether training happens is the hours a hospital takes off the floor to run it, so that is the column we publish.
| Mode | How it runs | What it costs in staff time |
|---|---|---|
| On site | A Pensieve engineer and a clinical lead work on the floor with a cohort, on your rehearsal site, in the department where the work happens. | Staff are off the floor in cohorts, so the hospital carries roster cover for the session. This is the most expensive mode in time and the only one that reaches people who will not read anything. |
| Remote | Live sessions over video against the same rehearsal site, with a trainer watching each person carry out the task on screen. | No travel and no cover for a visiting trainer, but the session still occupies a shift slot and has to be scheduled against the rota. |
| Self-paced | Written lessons and open access to the rehearsal site, taken in any order, repeatable as often as a person wants. | No scheduled time at all. The hospital carries no roster cover, and nobody waits for a cohort to fill. It is also the mode that is easiest not to do. |
Why there are no hours on this page
A training figure depends on your configuration, your rota, and how many of your staff have used a computerised record before. Any number we printed here would be an average taken from other hospitals, which is not a number you can plan against.
At the survey, we count your roles, your sites, and the cohorts they divide into, and give you the figure for your building. It goes in the engagement, where we are accountable for it.
Cohort sizes and session lengths are set per engagement.
Cohort sizes, session lengths, and the rate card for on-site delivery are set for each engagement and confirmed in the contract.