Soigneur FHIR Implementation Guide
0.1.0 - ci-build Germany flag

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

: Soigneur Communication Categories - XML Representation

Active as of 2026-11-14

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="cc-comm"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem cc-comm</b></p><a name="cc-comm"> </a><a name="hccc-comm"> </a><p>This case-sensitive code system <code>https://fhir.soigneur.coach/fhir/CodeSystem/cc-comm</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">llm-turn<a name="cc-comm-llm-turn"> </a></td><td>LLM interaction turn</td><td>One captured agent turn (briefing, review, ask exchange).</td></tr><tr><td style="white-space:nowrap">chat-notice<a name="cc-comm-chat-notice"> </a></td><td>Chat system notice</td><td>Durable in-app chip (profile / coach-notes / prescriptions updated) — ADR 0044.</td></tr><tr><td style="white-space:nowrap">chat-card<a name="cc-comm-chat-card"> </a></td><td>Open HITL card</td><td>Durable record of an interactive pause card (questionnaire / approval / clarify): the resume key + card payload the chat rehydrates after navigation — open/closed is positional (issue #391, ADR 0116).</td></tr><tr><td style="white-space:nowrap">handoff-kickoff<a name="cc-comm-handoff-kickoff"> </a></td><td>Hand-off kickoff divider</td><td>The auto-sent same-thread skill hand-off kickoff (plan builder / FTP check) as a system-role divider turn — never an athlete echo; still re-kickable like a trailing unanswered preamble (issue #507, ADR 0115 amendment).</td></tr><tr><td style="white-space:nowrap">invitation<a name="cc-comm-invitation"> </a></td><td>Invitation</td><td>Onboarding / invitation message.</td></tr><tr><td style="white-space:nowrap">reminder<a name="cc-comm-reminder"> </a></td><td>Reminder</td><td>Reminder / nudge message.</td></tr><tr><td style="white-space:nowrap">in-app<a name="cc-comm-in-app"> </a></td><td>In-app channel</td><td>Communication.medium for coach-ask chat (not email/ACS) — ADR 0044.</td></tr><tr><td style="white-space:nowrap">conversation-header<a name="cc-comm-conversation-header"> </a></td><td>Conversation header</td><td>One per coach thread: archive title + sort key (ADR 0046).</td></tr><tr><td style="white-space:nowrap">conversation-summary<a name="cc-comm-conversation-summary"> </a></td><td>Conversation summary</td><td>Hidden rolling summary of a coach thread's covered prefix — long-thread continuity (issue #172).</td></tr><tr><td style="white-space:nowrap">thread-ask<a name="cc-comm-thread-ask"> </a></td><td>Ask thread</td><td>Freeform coach-ask conversation (ADR 0062).</td></tr><tr><td style="white-space:nowrap">thread-briefing<a name="cc-comm-thread-briefing"> </a></td><td>Briefing thread</td><td>Daily readiness briefing conversation (ADR 0062).</td></tr><tr><td style="white-space:nowrap">thread-workout-review<a name="cc-comm-thread-workout-review"> </a></td><td>Workout-review thread</td><td>Post-ride review conversation (ADR 0062).</td></tr><tr><td style="white-space:nowrap">thread-ftp-check<a name="cc-comm-thread-ftp-check"> </a></td><td>FTP-check thread</td><td>FTP cross-check conversation — propose-then-accept over the deterministic estimates (issue #228, ADR 0027/0054).</td></tr><tr><td style="white-space:nowrap">thread-plan<a name="cc-comm-thread-plan"> </a></td><td>Plan thread</td><td>Plan-authoring conversation — build-plan and adapt-plan share the kind; threads are created through the build entry (WS7, ADR 0115).</td></tr><tr><td style="white-space:nowrap">thread-strength-plan<a name="cc-comm-thread-strength-plan"> </a></td><td>Strength-plan thread</td><td>The separate strength-domain plan-authoring conversation (WS7, ADR 0096).</td></tr><tr><td style="white-space:nowrap">thread-design-workout<a name="cc-comm-thread-design-workout"> </a></td><td>Workout-design thread</td><td>Single-workout authoring conversation (WS7).</td></tr></table></div>
  </text>
  <url value="https://fhir.soigneur.coach/fhir/CodeSystem/cc-comm"/>
  <version value="0.1.0"/>
  <name value="CcComm"/>
  <title value="Soigneur Communication Categories"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-11-14T19:13:43+00:00"/>
  <publisher value="Soigneur"/>
  <contact>
    <name value="Soigneur"/>
    <telecom>
      <system value="url"/>
      <value value="https://soigneur.coach"/>
    </telecom>
  </contact>
  <description value="Communication.category values (05 14.1, 04 15.22)."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="DE"/>
      <display value="Germany"/>
    </coding>
  </jurisdiction>
  <copyright
             value="Copyright (c) Soigneur. Licensed under CC0-1.0 (public domain dedication). FHIR(R) is the registered trademark of HL7 and is used with permission."/>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <count value="16"/>
  <concept>
    <code value="llm-turn"/>
    <display value="LLM interaction turn"/>
    <definition
                value="One captured agent turn (briefing, review, ask exchange)."/>
  </concept>
  <concept>
    <code value="chat-notice"/>
    <display value="Chat system notice"/>
    <definition
                value="Durable in-app chip (profile / coach-notes / prescriptions updated) — ADR 0044."/>
  </concept>
  <concept>
    <code value="chat-card"/>
    <display value="Open HITL card"/>
    <definition
                value="Durable record of an interactive pause card (questionnaire / approval / clarify): the resume key + card payload the chat rehydrates after navigation — open/closed is positional (issue #391, ADR 0116)."/>
  </concept>
  <concept>
    <code value="handoff-kickoff"/>
    <display value="Hand-off kickoff divider"/>
    <definition
                value="The auto-sent same-thread skill hand-off kickoff (plan builder / FTP check) as a system-role divider turn — never an athlete echo; still re-kickable like a trailing unanswered preamble (issue #507, ADR 0115 amendment)."/>
  </concept>
  <concept>
    <code value="invitation"/>
    <display value="Invitation"/>
    <definition value="Onboarding / invitation message."/>
  </concept>
  <concept>
    <code value="reminder"/>
    <display value="Reminder"/>
    <definition value="Reminder / nudge message."/>
  </concept>
  <concept>
    <code value="in-app"/>
    <display value="In-app channel"/>
    <definition
                value="Communication.medium for coach-ask chat (not email/ACS) — ADR 0044."/>
  </concept>
  <concept>
    <code value="conversation-header"/>
    <display value="Conversation header"/>
    <definition
                value="One per coach thread: archive title + sort key (ADR 0046)."/>
  </concept>
  <concept>
    <code value="conversation-summary"/>
    <display value="Conversation summary"/>
    <definition
                value="Hidden rolling summary of a coach thread's covered prefix — long-thread continuity (issue #172)."/>
  </concept>
  <concept>
    <code value="thread-ask"/>
    <display value="Ask thread"/>
    <definition value="Freeform coach-ask conversation (ADR 0062)."/>
  </concept>
  <concept>
    <code value="thread-briefing"/>
    <display value="Briefing thread"/>
    <definition value="Daily readiness briefing conversation (ADR 0062)."/>
  </concept>
  <concept>
    <code value="thread-workout-review"/>
    <display value="Workout-review thread"/>
    <definition value="Post-ride review conversation (ADR 0062)."/>
  </concept>
  <concept>
    <code value="thread-ftp-check"/>
    <display value="FTP-check thread"/>
    <definition
                value="FTP cross-check conversation — propose-then-accept over the deterministic estimates (issue #228, ADR 0027/0054)."/>
  </concept>
  <concept>
    <code value="thread-plan"/>
    <display value="Plan thread"/>
    <definition
                value="Plan-authoring conversation — build-plan and adapt-plan share the kind; threads are created through the build entry (WS7, ADR 0115)."/>
  </concept>
  <concept>
    <code value="thread-strength-plan"/>
    <display value="Strength-plan thread"/>
    <definition
                value="The separate strength-domain plan-authoring conversation (WS7, ADR 0096)."/>
  </concept>
  <concept>
    <code value="thread-design-workout"/>
    <display value="Workout-design thread"/>
    <definition value="Single-workout authoring conversation (WS7)."/>
  </concept>
</CodeSystem>