Misc
Basic Resource Type
Definition and Purpose
Not all profiles needed in the NOMA FHIR API are available - either in FHIR in general, or in the FHIR verson currently in use. In such a case, profiles have to be created extending the "Base" profile.
Yet, if more than one such profile is created - such as Nutrition Product or, at a later stage, PhPID, it is difficult to understand what type a certain element acutally is, since all elements of all profiles extending "Basic" will have the same "ResourceType", namely "Basic"
This code system was created to be able to differentiate between elements with "ResourceType" "Basic".
Example, for a Nutrition Product:
"code" : {
"coding" : [ {
"system" : "https://api.legemiddelverket.no/FHIR-R4/CodeSystem/4aaedf1f-a66e-4c82-a8c0-de28eb4eaa2a",
"code" : "1",
"display" : "Nutrition Product"
} ]
Example
Nutrition Product
For more examples, see Basic Resource Type Examples
Usage
Current usage: None
Future usage: In Nutrition Product, (PhPID, PhPID Set)
Code system source
NOMA
Godkjenningstatus (for koder)
Definition and Purpose
Status of approval of a term in a code system
Examples
Usage
Current usage: Code System concepts (e.g. ATC)
Future usage: See above
Code system source
Internt NOMA
Record Status
Definition and Purpose
Status of a concept or a code system (RMS). Not used in the FHIR API, since only concepts and code system with record status "CURRENT" are published.
Examples
Current, Procvisional
For more examples, see Record Status Exampless
Usage
Current usage: None
Future usage: Nome