# `SnomedConcept`

A SNOMED CT concept's identifier, its Verhoeff check digit passing: `22298006`. Health data.

[Health](types.md#health); not ordered; personal data (health); since Jadpo 0.1.0.

## Make one

Build one from its text, `SnomedConcept("22298006")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: SnomedConcept)` reads one from its text; text that isn't one at all fails `malformed`, such as `22298007`, `22298010` or `022298006`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `22298006` | `"22298006"` |
| `73211009` | `"73211009"` |
| `138875005` | `"138875005"` |
| `999480561000087100` | `"999480561000087100"` |

It is stored in one column named for the field, of type `text`. `138875005` is stored as `'138875005'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `22298006` | `22298006` |
| `73211009` | `73211009` |
| `138875005` | `138875005` |
| `999480561000087100` | `999480561000087100` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.