MPox: Exposure.where

[oliveregger]

Exposition.wo optional before wann und wie mit vier Angaben

• CH/LI (Checkbox)
• Ausland (Auswahl Dropbox mit Ländern)
• Genauer Ort (CH/LI und Ausland): Textfeld
• Unbekannt (separate Box)

Aktuell ist das unbekannt separat, es ist (noch) nicht deifniert ob sich das auf Ort bzw Land oder beides bezieht.

[oliveregger]

if CH/LI (Checkbox) is coded together, how should we model that? country=CH? We can't combine both as a country code directly

[oliveregger]

Implemented — Exposition "wo"

Form (ChEkmQuestionnaireExposureWhere, new modular assemble-child)

Assembled into the Mpox root before "wann" and "wie", per the four items of this issue:

linkId	type	note
exposureWhereChLi	choice, check-box, 1 option	"CH/LI". Form-only — the logical model has no inland/ausland element ("on the structured level we will not have inland/ausland as separate checkbox items", decision of 1 June, recorded in ChEkmExposureForm), so it has no definition
exposureWhereCountry	choice, autocomplete	"Ausland, Land", bound to ChEkmCountryCodes; hidden while CH/LI is ticked
exposureWherePreciseLocation	string	"Genauer Ort (CH/LI und Ausland)"
exposureWhereUnknown	choice, check-box, 1 option	"Unbekannt", separate box

Two rendering notes that cost some digging, in case other forms hit them:

• The two check-boxes are choice items with a single valueString answerOption, not boolean items. A boolean renders as a Yes/No radio pair, and even with itemControl = check-box the Smart Forms renderer puts the label in its left label column and the box on the right — a choice check-box renders "☐ label" on one line, like the paper form. repeats = true additionally makes un-ticking remove the answer instead of leaving false behind.
• The option label is a plain string, not a Coding: a Coding would have to carry the terminology's own display ("Switzerland" instead of "Schweiz/Liechtenstein (CH/LI)"), which the validator flags. Inline option labels are translated via translation extensions on _valueString, baked into the de/fr/it preview questionnaires by scripts/build-lang-questionnaire.py.

There is no way to place two questions side by side (e.g. the CH/LI box next to the Ausland dropdown): SDC's layout vocabulary is only itemControl (list/table/htable/atable/gtable/grid/…), choiceOrientation, rendering-style/rendering-xhtml on labels and columnWidth; of those, only gtable puts distinct questions in columns (labels then become column headers), and this renderer implements only gtable + grid. Left with the stacked layout.

FHIR mapping (ChEkmExtExposureAddress)

• Land → valueAddress.country as the ISO 3166 code plus the coded country in country.extension[countryCoding] (iso21090-codedString — same requirement CH ELM puts on Patient.address.country; note iso21090-SC-coding is deprecated in the extensions package in favour of codedString).
• Genauer Ort → valueAddress.city.
• Unbekannt → valueAddress.extension[unknown] = data-absent-reason#asked-unknown (new slice).

ChEkmBundleHepatitisC was adapted to the same pattern (country = "NP" + codedString Coding, replacing the free-text "Nepal").

Extraction (RuleSetExposureWhere)

The whole extension is built at extraction time via the FHIR Type Factory (%factory.Address / withProperty / withExtension) on the SDC template-extract carrier, because a pre-declared extension[exposureAddress] cannot be context-gated as a whole (the gate would be an illegal sub-extension next to value[x]) and the country Coding lives on the unreachable _country slot.

Behaviour — "Unbekannt" does not suppress the other answers, as long as its meaning is undecided:

answered	extracted valueAddress
country + Ort	{city, country, _country.extension[codedString]}
CH/LI + Ort	{city, country: "CH", _country.extension[codedString]}
Unbekannt only	{extension[data-absent-reason]}
Unbekannt + country/CH-LI + Ort	both — address content and extension[data-absent-reason]
nothing	no extension at all

Verified end-to-end through the reference $extract engine for all of the above; the combined case was additionally validated against ch-ekm-document-mpox with the FHIR validator (no complaint — data-absent-reason carries no invariant against coexisting content). IG Publisher build: 0 errors.

Open points

1. Meaning/scope of "Unbekannt" — still undefined whether it refers to the country, the precise location or both (the point raised in this issue). Currently modelled as the whole "wo" is unknown, with the data-absent-reason on the Address, and nothing entered is discarded. Note this is semantically contradictory when content is present (data-absent-reason means "the value is missing"); once the scope is decided, the cleaner encoding is to move the DAR onto the specific element (country or city).
2. CH/LI collapses to country = CH — the paper form's single check-box cannot distinguish Liechtenstein. If LI must be reportable, add a second answerOption (LI) to the check-box and read the answer instead of the fixed CH — a form-only change plus one iif in the extraction rule.

[oliveregger]

Diskussion Telco: 17.18

Es gibt nur Abfrage nach Land (nicht kombiniert zwei Länder), und wird als Countryode angegeben

Aber Texte anpassen:
Was ist der meistwahrscheinlichste Ort der Ansteckung.

Pflichtfeld Angaba Land mit Popup Schweiz und Lichtenstein zuoberst, plus unbekannt auswähbar

Genauer Ort auch als Pflichtfelder:
-> Verschlankung mit unbekannt als Dropdown und Freitextfeld für Ort möglich

[oliveregger]

CH/LI kann nicht codiert angegeben werden, macht Sinn das zu separieren, das heisst aber nicht dass es im UI auch Support geben könnte CH oder LI als Default zu setzen (jetzt versucht via Positionierung im Popup).

[oliveregger]

tb reviewed at next meeting