Projo FHIR Documentation
0.1.0 - ci-build
Projo FHIR Documentation
0.1.0 - ci-build
Projo FHIR Documentation - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://projo.evoleen.com/fhir/ValueSet/plan-slot-kind-vs | Version: 0.1.0 | |||
| Draft as of 2024-01-01 | Computable Name: PlanSlotKindVS | |||
Copyright/Legal: Copyright (c) Projo. Licensed under CC0-1.0 (public domain dedication). FHIR(R) is the registered trademark of HL7 and is used with permission. This IG references WhatsApp(R), a trademark of Meta Platforms, Inc., for descriptive purposes only. |
||||
Allowable kinds for the plan-slot extension's kind sub-extension.
References
https://projo.evoleen.com/fhir/CodeSystem/plan-slot-kind version 📦0.1.0
Expansion performed internally based on codesystem Projo Plan Slot Kind v0.1.0 (CodeSystem)
This value set contains 4 concepts
| System | Code | Display (en) | Definition | JSON | XML |
https://projo.evoleen.com/fhir/CodeSystem/plan-slot-kind | onboarding | Onboarding | Initial intake plan; applied on Patient just-created or first inbound. | ||
https://projo.evoleen.com/fhir/CodeSystem/plan-slot-kind | default | Default | Steady-state plan; applied when no onboarding slot exists or onboarding is complete. | ||
https://projo.evoleen.com/fhir/CodeSystem/plan-slot-kind | re-engagement | Re-engagement | Plan applied when a returning patient reattaches with no-active-cr. | ||
https://projo.evoleen.com/fhir/CodeSystem/plan-slot-kind | onboarding-routing | Onboarding routing | Router-side PlanDefinition (CQL-driven clinical routing), pinned via canonical|version (ADR 0007). |
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 |