Skip to main content

How to add a clinical code to something sent to the GP record

Written by Sonja Gebhardt

A SNOMED CT code tells the GP system what a recorded item means. This guide covers the current code picker on client records and the more guided code control on form questions.

It does not cover checking whether filing succeeded; use the Clinical Systems queue for that. Structured consultation codes come from their template, as explained in How to record a consultation.

Add a code to a client record

  1. Open the client and select the Client record tab.

  2. Select Create new, then choose Contact, Appointment, Note or Action.

  3. Under Clinical record, tick Save to clinical record.

  4. Check the Destination. Joy offers Detect automatically and any available clinical systems.

  5. Under SNOMED CT codes, select Search SNOMED CT code.

  6. Search by a clinical description or an exact numeric code.

  7. Select the result you need. You can add more than one code.

  8. Select Save record.

Type at least two characters. Before that, the picker says Type at least 2 characters to search the catalogue.

You cannot type and save a free code. You must select a result offered by the catalogue. If there is no result, the app says No catalogue code matches “[search]”. This code cannot be added.

After saving, the code is carried with the item queued for the clinical record. Open the timeline item to see the chosen code under SNOMED CT codes and the current filing status.

Add a code when sending an existing record

Open an unsent timeline item. In its Clinical record section, choose codes under SNOMED CT codes, then select Send to clinical record.

Joy confirms with Sending to clinical record and The record has been queued for transmission.

A queued or sent item is not proof that the GP record has applied it. Look for Filed to clinical record or check the Clinical Systems queue.

Codes on form questions

The form builder has a Clinical code row on each question except a section heading.

  1. Select Add a code.

  2. Select Suggest from the question to ask Joy for a shortlist based on the question wording, or search the catalogue yourself.

  3. Review Best matches or Closest codes.

  4. Select a code from the offered list.

  5. Select Done.

Curated codes are marked Commonly used here and rank ahead of usage-only codes when the match quality is equal. The suggestion process can only choose from its server-built shortlist; it cannot invent a code.

Most questions should stay uncoded. The screen says None — the answer won't be coded in the GP record. Most questions don't need one. It can also report No code needed when the question has no suitable clinical concept. Use Leave uncoded rather than choosing a close but incorrect result.

If suggestions cannot be fetched, the app says Couldn't fetch suggestions. Search the catalogue below instead.

Units for coded numbers

A number has no clinical meaning without its unit. When you code a number question, Measured in appears.

Joy suggests a unit from the question wording where it can, or uses a plain count when the wording implies no measurement. Check the unit and change it if needed.

The code and unit are saved together. If a coded number has no valid unit, the code is not saved. The warning reads Pick a unit — a number with no unit can't be coded, so the code won't be saved.

Units apply to coded number questions only. Text, date, choice and checkbox questions do not carry one.

What the code changes

The code travels with an item that is filed to the GP record and identifies the clinical concept for that item or answer. It does not change the wording you entered in Joy.

For consultation records, codes are derived from the assigned consultation template and completed answers rather than chosen in the consultation form.

Capturing a code on a staff-built form question is available today. Filing that individual coded form answer into the GP record is not yet built, so do not treat the saved question code as evidence that the GP record received it.

Related guides

Did this answer your question?