Skip to content

Source Value Record Profile

Canonicalhttps://fhir.apps.health/StructureDefinition/nexus-core-source-value-record
Statusdraft · 1.33.0
BaseBasic (constraint)
SourceFSH · JSON

Source values that have no record of their own to sit on: a whole source category this guide does not model, or a value with no resource to carry it. One per patient per source category, coded under the source's namespace, with the values in the nexus-source-value extension. Nothing computes on it. First pass.

Overview

Handbook: Source values

The narrative treatment -- what this is for, why it is shaped this way, and how it is used.

⚠ FIRST PASS -- do not treat this as a contract. The profile is #draft.

Overview

Source values that have no record of their own to sit on. A source value belongs on the record it describes, in the nexus-source-value extension. When there is no such record -- a whole source category this guide does not model, or a value about the patient that no resource here carries -- this Basic holds the values, one per patient per source category.

Fact Element
The source category code.coding: system = https://fhir.apps.health/source-field/<source>, code = the source's name for the category
The patient subject
When the values were recorded here created (the effective date)
The values the nexus-source-value extension, one child per source field

Nothing computes on these values: they are not searched, and no decision support or measure reads them. A client that saves the record keeps the extension it read. For an import, the Provenance of the import names the file, the importer and the time.

The profile is declared-only: it applies to a Basic that names it in meta.profile. Basic also carries App State, which is declared-only too, so a reader tells the two apart by meta.profile. A SMART scope names a resource type, not a profile, so an app granted basic scopes for App State can read, write and delete these records as well; limiting who may write them is a server decision the profile cannot express.