CDS Content Status Tag CodeSystem Code system¶
| Canonical | ../CodeSystem/nexus-cds-content-status |
|---|---|
| Status | draft · 1.26.0 |
| Content | complete |
| Source | FSH · JSON |
The state of the decision-support CONTENT a suggestion task was projected from, carried as a tag on
Task.meta.tag where this is the tag's system. Distinct from Task.status, which describes the
WORK rather than the rule content behind it.
Presence is the assertion; absence is not. A task carrying unsigned-draft was raised from
content loaded without requiring clinical sign-off, and a consumer should surface it as such. A task
carrying no tag under this system asserts nothing: it may come from a producer that requires
sign-off, or from one that does not write this system at all, and the two are indistinguishable.
Never read an absent tag as "the content was signed".
It records the check, not the pack. The tag says what the loading instance verified. Content that happens to carry a sign-off record is still tagged when the instance that loaded it had the sign-off requirement switched off.
Not a security label, and not a substitute for one. Machine-authored tasks carry AIAST in
meta.security; that says who wrote the suggestion. This says what state the rule behind it was in.
The two are orthogonal and neither can be inferred from the other.
At most one coding under this system. Writers set meta.tag whole rather than appending; a
reader should take the first and not reconcile two.
Not bound from any profile. meta.tag is open on every resource and is not sliced in this
guide. This system is declared so the tag's Coding.system resolves, not to add an element to the
Task profile.
| Code | Display | Definition |
|---|---|---|
unsigned-draft |
Unsigned draft CDS content | The decision-support content this task was projected from was loaded WITHOUT requiring clinical sign-off. It says the loading instance did not check for a sign-off, not that the c… |