Companion
Core 0.4.2Organises pre-visit information and distinguishes answers from gaps and uncertainty. In the connected workflow, it transfers a summary to Clinic Assistant and prepares an update.
Explore it in the v2 workflow →RHEUMANEXT V2 · BEHAVIOUR AND INFORMATION PROVENANCE
See where
the result comes from.
Explicit rules, sources and gaps. Move from a summary to an update and inspect what changes in the material for review.
Rules you can trace
The tools use defined rules and data structures. The same data, versions and actions produce a reproducible result. They are not a generative model or a system that learns from visitors.
Unknown information stays unknown. A gap is not converted into a negative answer, and a source entry and its later update remain distinct.
What v2 connects
In the connected workflow, Companion transfers specific material to Clinic Assistant. A question about missing information returns to Companion, and a prepared answer updates the clinician’s material after it is sent back.
Transfer follows user actions in one page’s memory, without saving to a server. Resetting, reloading and switching language restart the session. Standalone product examples keep their own state.
PRODUCT BEHAVIOUR
Four roles, a defined scope.
V2 identifies the new platform release. Core versions remain separate identifiers; their historical acceptances do not automatically extend to the new workflow.
Clinic Assistant
Core 0.1.8The clinician’s workspace: receiving the summary, sources, gaps, a question and review of the update. The original information remains readable alongside the current material and action record.
Explore it in the v2 workflow →RheumaCheck
Core 0.1.5Receives symptoms from Companion through an explicit adapter. Adding the duration of morning stiffness updates the input and missing-information list. Assessment remains withheld for this new case: scope and safety information are missing, and the input needs separate review and registration.
Explore it in the v2 workflow →RheumaCare
Core 0.1.3Uses a separate, complete case of diagnosed rheumatoid arthritis with treatment history. A missing tuberculosis assessment withholds the option map; adding the prepared fact from that same case triggers a recalculation. The clinician’s decision remains a separate, unrecorded element.
Explore it in the v2 workflow →What the technical checks cover
Consistency between inputs, views, sources and exports; transfer and return of an update; preservation of original entries and review state; and prevention of stale results after data changes. Checks also cover safety rules, the independence of standalone modes and Polish/English consistency.
These are software checks using synthetic data. They do not establish patient-care outcomes, full WCAG conformance or clinical effectiveness.
Boundaries for further connections
A symptom example does not automatically contain the rheumatoid arthritis diagnosis and treatment history required by RheumaCare. Those facts need their own source and review scope.
RheumaCheck receives symptoms through a versioned adapter; an update recalculates its result. Missing scope and safety information and the new-case registration gate still limit a full assessment. RheumaCare recalculates the separate RA case after the prepared tuberculosis information is added. This does not continue the hand-symptom patient’s history. Standalone product modes also remain available.
SEPARATE HISTORICAL MATERIALS
Earlier versions and their reviews
The registers below describe the exact materials at the time of their acceptance. They do not constitute acceptance of the new v2 workflow. Original archives and decisions remain preserved outside the application.
Companion 0.4.2
R3 · 2026-08-13
Historical material scope and identity
Round R3 of the owner’s product and content review. Scope: local synthetic examples.
614 accepted register entries
The count refers to register entries. It does not count clinical studies or patients and does not automatically represent software tests.
Source archivecompanion-review-v042.zip
SHA-256330a73a6aa31d287f4b4f03f20ddfe51e84eda2dd5bca90433b996e3dd09e2b5
Clinic Assistant 0.1.8
R4 · 2026-08-19
Historical material scope and identity
Round R4 of the owner’s product and content review. Scope: the exact package and its own built-in visit example.
38 accepted register entries
The count refers to register entries. It does not count clinical studies or patients and does not automatically represent software tests.
Source archiveclinic-assistant-review-v018.zip
SHA-256fa4a9ed2e3b733c15277bf8f69b2b96878718146fc85141d3a18a7f71b3dde94
The register compares 38 identifiers and material checksums with the sealed R4 catalogue. An earlier independent checksum declaration for the complete external register is unavailable.
RheumaCheck 0.1.5
· 2026-08-12
Historical material scope and identity
Acceptance of the clinical-content snapshot for continued synthetic design evaluation. Does not approve intended purpose or clinical effectiveness.
195 accepted register entries
The count refers to register entries. It does not count clinical studies or patients and does not automatically represent software tests.
Source archiverheumacheck-review-v015.zip
SHA-256963438b2069312a2c97a9fee166463e27c0d75368a8bb7209f0d542c522a7b60
Product version: 0.1.5. Rules and case-library version: 0.1.4.
RheumaCare 0.1.3
R4 · 2026-09-07
Historical material scope and identity
Round R4 of the owner’s review. Scope: only the local synthetic core from the exact V0.1.3 package under RHEUMACARE-V013-CURRENT-STATE-V1.
43 accepted register entries
The count refers to register entries. It does not count clinical studies or patients and does not automatically represent software tests.
Source archiverheumacare-review-v013.zip
SHA-256777b701299961294477cbd35667b86f5f8862bbea83d20e85f392d2edcea3f14
Historical scope contract: RHEUMACARE-V013-CURRENT-STATE-V1
RheumaCare: the retained historical gap
The identity of the retained version and consistency between its demonstration and core are separate from full historical directory immutability. That full verification remains unconfirmed.
Evidence-gap details
The current state was sealed with the historical gap retained. Some material was checked through metadata only, and two historical comparison TSV files are unavailable in the retained evidence. Full historical immutability: NOT_RECONFIRMED.
The later external R4 register contains 43 acceptances for the exact local synthetic V0.1.3 core under RHEUMACARE-V013-CURRENT-STATE-V1. The earlier 43 incomplete entries still document the state at sealing. The R4 acceptances do not restore missing evidence.
Historical RheumaCare R1 presentation
The standalone RheumaCare R1 presentation was accepted locally on 8 September 2026 using synthetic data. This external acceptance is separate from the core R4 and the new RheumaNext v2 workflow.
rheumacare-presentation-r1-review.zipb4b1702821fbb6b49ca1dc23b38fb72a51a598e03daf70188c6c0a1cbac7a32f
RHEUMACARE_PRESENTATION_R1_LOCAL_ACCEPTANCE_2026-09-08.mdbc40ee04ec6e0d72a47f54f9c3f51715cfb287aec04be04eb60a5f3bb5d0915a
Earlier statuses and test results remain historical. New checks do not replace missing TSV files or establish clinical validation.
DEVELOPMENT DIRECTION
Next Best Therapy
A direction for further work on treatment-review support. It requires separate development and validation. Current RheumaCare organises the context and constraints of options.
Explore collaboration →USE SCOPE
Controlled synthetic examples
The workflow lets users explore the product’s behaviour. Clinical use, medical records, real-person data and pilots are outside the available scope. Further applications require appropriate assessments, validation and decisions.
Safety principles →