Skip to main content

Working in GP Records

Open GP Records with your team key. Search for a person by name, local ID, condition or care need.

Record a consultation​

Select a patient, then choose New consultation. Enter a title, contact type and notes. Save draft stores unfinished notes in your team world. Save consultation adds a saved entry to the patient journal.

The Consultations tab lists previous contacts. Expand an entry to read its narrative. Entries created through this editor have Open for editing. Saving an edit updates that record and its version. A conflicting edit is rejected, so reload the entry before trying again.

Unsubmitted title, contact type and note text remain in the current browser session for that patient. Use Save draft before moving to another device. New consultation starts a separate note. The simulator does not provide clinical recommendations or a production clinical signing process.

Maintain problems and allergies​

Open Problems, then Add problem. Enter the problem name and optionally a code and onset date. Saving updates the patient's active-problem summary. Edit / resolve lets you correct or resolve an entry; choose Active and resolved to see its history or reactivate it.

Open Allergies, then Add allergy to record an allergen and optional reaction. Active entries appear in the patient banner. Inactive entries remain in history. An empty list means no allergy information has been recorded; it does not confirm that the patient has no allergies.

Problem and allergy changes carry team attribution and version history and are visible to the hospital, community and pharmacy in the same team world. Historical entries without a recorded author retain that distinction.

Follow up requests​

Medication shows new prescription requests and their pharmacy status alongside recorded medication history. Open in pharmacy takes you to the receiving system. Refer to hospital creates a referral the hospital can review and accept.

After requesting a test and advancing simulation time, open its entry in Results and choose Mark reviewed. GP review is recorded with your team's attribution. Follow-up tasks can be reviewed, accepted and completed from their record details.

Work the appointment book​

Choose Appointment book before or after selecting a patient. The diary groups timed slots into clinician sessions. Filter by date, clinician, or AM and PM. Dates and times use the simulation's UTC clock.

Select an available slot, find the patient, and enter the reason. The session supplies the clinician, location, contact type, and duration. A booked slot offers arrival, completion, and cancellation. Cancelled slots become available again; completed bookings remain in history.

Use Create session to add sessions. A free slot can be blocked for protected time and unblocked later. The server rejects overlapping sessions and bookings. Read Appointment sessions and slots for the complete workflow and request fields.

Explore the population​

New teams inherit the published synthetic population, including the authored life histories with personal context and distinct past contacts. Before a large population is published, a team starts with 500 people. Existing patient work is preserved when an older world is expanded. See the population guide for generation and public-data sources.

Try Nina Brooks, a child whose appointment arrangements involve her parent; Yasmin Ahmed, taking over her own appointment arrangements as she starts college; or Frank Walsh, coordinating longer appointments with community transport. Open their journal and consultation history to follow their earlier contacts.

Build against the same records​

Use POST /api/sites/gp/actions with your bearer key. A consultation action contains type: "save_consultation", patientId, title, text, mode and consultationStatus, either draft or saved. Updates also require resourceId and expectedVersion.

A session-based book_appointment action supplies sessionId, sessionVersion, startsAt, patientId, and title. The session defines its duration, clinician, and contact type. arrive_appointment, complete, and cancel_appointment take a resource ID and support expectedVersion.

Use save_problem with patientId, title, and problemStatus (active or resolved); problemCode and onsetDate are optional. Use save_allergy with patientId, title, and allergyStatus (active or inactive); reaction is optional. Editing either resource requires resourceId and expectedVersion. Their records remain in history after resolution or deactivation.

Read the book with GET /api/sites/gp/appointments?date=2026-09-10. It returns appointments and the names needed to display them. Patient consultation records remain available through the normal patient view.

Open a patient and select Results in GP Records, or Results review in the hospital chart. Both EPRs show the same laboratory history for that patient and team world.

The synthetic history includes FBC, U&E, HbA1c, LFT, CRP and lipids, with six sample dates per panel. GP Records shows each analyte's latest value, units, sample date, previous value, and illustrative reference interval. Hospital Results defaults to a flowsheet with sample dates in columns and a panel navigator. Lab results are separate from wearable observations. Pending requests and other investigations remain under their own disclosure.

Choose View trend beside one test, or tick several tests and choose Graph selected. Each test gets its own chart and units in a popup. Change the history period or expand View values to inspect the dated values. Close the popup with its Close button or Escape.

All values and reference intervals are fictional simulation data. Historical dates respect the patient's date of birth. Existing team worlds receive each patient's history on first opening that record, without replacing their own records or expanding every large cohort at startup.