Patient Monitoring Outcome FHIR Implementation Guide, published by My Organization. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/patient-monitoring/ and changes regularly. See the Directory of published versions
Official URL: http://hl7belgium.org/fhir/patient-monitoring/ValueSet/continence-level | Version: 0.1.0 | |||
Active as of 2025-10-15 | Computable Name: ContinenceLevel | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.54.48.7 |
LOINC codes to represent the level of continence reported
References
Expansion from tx.fhir.org based on Loinc v2.81
This value set contains 5 concepts
System | Code | Display (en) | JSON | XML |
http://loinc.org | LA126-5 | CONTINENT-Complete control [includes use of indwelling urinary catheter or ostomy device that does not leak urine or stool] | ||
http://loinc.org | LA127-3 | USUALLY CONTINENT-BLADDER, incontinent episodes once a week or less; BOWEL, less than weekly | ||
http://loinc.org | LA128-1 | OCCASIONALLY INCONTINENT-BLADDER, 2 or more times a week but not daily; BOWEL, once a week | ||
http://loinc.org | LA129-9 | FREQUENTLY INCONTINENT-BLADDER, tended to be incontinent daily, but some control present (e.g., on day shift); BOWEL, 2-3 times a week | ||
http://loinc.org | LA130-7 | INCONTINENT-Had inadequate control BLADDER, multiple daily episodes; BOWEL, all (or almost all) of the time |
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 |