FAP Logbook — a role-based logbook for the MBBS Family Adoption Programme

The MBBS Family Adoption Programme asks every student to build a longitudinal relationship with an adopted family, under the supervision of a faculty leader, coordinated by a department admin, and reviewed in due course by an examiner. On paper, that four-way relationship is held together by loose registers, individual notebooks and whatever a student happens to have written down before an exam. FAP Logbook replaces that paper trail with a single role-based digital record built for community medicine departments running the programme end to end. Clinoble describes it in one line as a role-based logbook for the NMC-mandated MBBS Family Adoption Programme, covering student, leader, admin and examiner.

What breaks when the Family Adoption Programme runs on paper

Paper-based FAP records fail in predictable ways. A student's notebook can be misplaced between the field visit and the departmental file, and once it is gone the underlying record of that engagement is gone with it. A faculty leader signing off on a stack of logbooks at the end of a term has no easy way to check an entry against what was actually observed at the time it was written, so sign-off becomes an act of trust rather than a documented step. An admin trying to compile a department-wide picture of programme activity across batches has to physically collate many individual books, a process that is slow, error-prone and hard to repeat consistently across cohorts. And an examiner sitting down to assess a student's engagement with the programme is often working from a single handwritten book with no independent way to cross-check dates, continuity or authorship.

None of these are dramatic failures on their own. They are quiet, structural gaps in traceability that accumulate until the day someone needs a complete, defensible record and cannot produce one.

FAP Logbook is built around a simple premise: if a record is entered digitally, tied to a role and timestamped at the point of creation, most of that fragility disappears. The programme's four participants, student, leader, admin and examiner, each get a view suited to what they are actually responsible for, and every entry feeds into a structure the department can rely on later.

Who this is for

FAP Logbook is built for community medicine departments in Indian medical colleges running the Family Adoption Programme as part of the MBBS curriculum. That includes departmental heads and phase coordinators who own the programme administratively, faculty who supervise student groups as FAP leaders, the students themselves who carry out the family engagements, and the examiners who later review that engagement as part of assessment. Deans and college leadership looking at how the programme is documented across departments are also a natural audience, because the platform is designed to make that documentation legible at a glance rather than leaving it buried in individual paper registers.

Four roles, four views

What a single entry carries

Every entry in FAP Logbook carries the same core structure regardless of who made it. It is attributed to a named student, associated with the adopted family that student is responsible for, stamped with the moment it was created rather than the moment it was copied out, and marked with whether the supervising leader has reviewed it. The narrative content of the visit sits alongside that structure rather than replacing it, so the descriptive part of the record, what the student observed and did with the family, stays in the student's own words while the surrounding metadata stays consistent across the whole department.

That consistency is the point. It is what allows entries made by different students, in different batches, under different leaders, to be read side by side without someone first having to normalise them by hand.

How records aggregate for the department

Individual entries do not stay isolated in one student's account. Because every entry carries a role, a student identity and a leader review status, the same underlying data can be read at the level of a single family engagement, a single student's cumulative record, a leader's group of students, or the department as a whole. That aggregation is what turns a pile of individual logs into something a department can actually use: a coherent, queryable record of programme activity that a departmental head or dean can review without reconstructing it by hand from paper registers each time it is needed.

FAP Logbook makes no promise about any particular regulatory or assessment outcome. What it does is give a department a structured, role-attributed record to draw on when the programme's documentation is reviewed, rather than leaving that record scattered across notebooks that were never designed to be read together in the first place.

What FAP Logbook is not

It is worth being precise about the boundaries. FAP Logbook is a record-keeping and workflow tool for an academic programme. It holds no clinical decision logic, produces no clinical output, and offers no interpretation of anything a student writes down about a family. Nothing in the platform is intended to substitute for the judgement of the faculty who supervise the programme or the examiners who assess it. The department sets the standard for what a good entry looks like; the platform's job is to make sure that once such an entry exists, it stays attributable, ordered and retrievable.

Current status

FAP Logbook is live. The four-role workflow, student entry, leader review, admin oversight and examiner assessment, is operating as a working platform rather than a plan or a prototype. As with any tool supporting an academic programme, the underlying record structure continues to be refined based on how departments actually use it, but the core logbook, review and aggregation functions are in active use today. The platform is hosted at fap.clinoble.com.

Where FAP Logbook sits in Clinoble's work

FAP Logbook sits alongside the rest of Clinoble's work in health technology. The company's other products span screening tools, a teleconsultation platform for rural primary care, a public-health surveillance platform and a bilingual family preventive-health platform, all built on the same principle that a record is only useful if it can be trusted and retrieved later. Clinoble Innovations Private Limited is based in Hyderabad, Telangana, India, and has two Indian patent applications pending in quantitative clinical imaging, IND 202641088451 and IND 202641090786. FAP Logbook is the part of that portfolio aimed squarely at medical education rather than at patient care.

Related answers

Medical colleges using the logbook ask how the records it holds map to what NMC expects to see.

• How should a medical college keep Family Adoption Programme records for NMC reporting?