Soigneur FHIR Implementation Guide
0.1.0 - ci-build
Soigneur FHIR Implementation Guide
0.1.0 - ci-build
Soigneur FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.soigneur.coach/fhir/ValueSet/cc-nutrition-scope | Version: 0.1.0 | |||
| Active as of 2026-11-14 | Computable Name: CcNutritionScopeVS | |||
Copyright/Legal: Copyright (c) Soigneur. Licensed under CC0-1.0 (public domain dedication). FHIR(R) is the registered trademark of HL7 and is used with permission. |
||||
The fueling-prescription scopes (standing / single).
References
https://fhir.soigneur.coach/fhir/CodeSystem/cc-nutrition-scope version 📦0.1.0| Code | Display | Definition |
| standing | Standing | A routine the athlete will repeat; one standing order per routine slot (the upsert key). |
| single | Single | One-off advice for one target day; acknowledged once its day passes, never cancelled. |
Expansion performed internally based on codesystem Soigneur Nutrition Prescription Scope Codes v0.1.0 (CodeSystem)
This value set contains 2 concepts
| System | Code | Display (de) | Definition | JSON | XML |
https://fhir.soigneur.coach/fhir/CodeSystem/cc-nutrition-scope | standing | A routine the athlete will repeat; one standing order per routine slot (the upsert key). | |||
https://fhir.soigneur.coach/fhir/CodeSystem/cc-nutrition-scope | single | One-off advice for one target day; acknowledged once its day passes, never cancelled. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |