sos-portal-components-react 0.3.3 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +163 -139
- package/README.md +233 -233
- package/dist/EncounterJourneyPanel.d.ts.map +1 -1
- package/dist/EncounterJourneyPanel.js +5 -4
- package/dist/EncounterJourneyPanel.js.map +1 -1
- package/dist/encounter-journey.css +91 -91
- package/package.json +111 -110
package/CHANGELOG.md
CHANGED
|
@@ -1,139 +1,163 @@
|
|
|
1
|
-
# Changelog
|
|
2
|
-
|
|
3
|
-
## Unreleased
|
|
4
|
-
|
|
5
|
-
## 0.
|
|
6
|
-
|
|
7
|
-
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
## 0.3.
|
|
42
|
-
|
|
43
|
-
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
## Unreleased
|
|
4
|
+
|
|
5
|
+
## 0.4.0 - 2026-11-14
|
|
6
|
+
|
|
7
|
+
- Verify the full 33 component tests and three required dependency contracts,
|
|
8
|
+
typecheck/build, source/emitted privacy and all six JavaScript public entries
|
|
9
|
+
plus CSS against the independent registry cohort. This release preserves
|
|
10
|
+
the existing shared API; it does not incorporate UHC components.
|
|
11
|
+
|
|
12
|
+
- Require the independent dependency gate in the normal check: reject GDC
|
|
13
|
+
declarations and aliases, source/declaration/emitted imports or re-exports,
|
|
14
|
+
and every transitive registry lock entry.
|
|
15
|
+
|
|
16
|
+
- Consume the published FHIR and SOS Data 0.7 contracts through registry-only
|
|
17
|
+
dependencies, preserving the shared UI API and the existing neutral
|
|
18
|
+
Antifraud renderer.
|
|
19
|
+
|
|
20
|
+
- Pin the reviewed SOS Data contract version used by the shared journey
|
|
21
|
+
renderer so dependency resolution does not reinstall an older catalog.
|
|
22
|
+
|
|
23
|
+
## 0.3.4 - 2026-11-12
|
|
24
|
+
|
|
25
|
+
- Render provider-supplied organization/service labels for authorized foreign history without exposing service-reference internals or mutation controls.
|
|
26
|
+
|
|
27
|
+
- Keep other-organization Encounter history read-only in the shared journey action selector. Document consent-free professional encounter traceability, scoped history read grants and the full IPS permission catalog.
|
|
28
|
+
|
|
29
|
+
## 0.3.3 - 2026-11-11
|
|
30
|
+
|
|
31
|
+
- Add controlled, host-authorized Encounter journey and transfer components, including persisted response validation and read-only Personal presentation. Retain the UHC transfer console through a compatibility wrapper.
|
|
32
|
+
- Recover the shared person/animal clinical-section, permission and US Core STU6 contract; distinguish existing views from the pending complete example lifecycle.
|
|
33
|
+
|
|
34
|
+
## 0.3.2 - 2026-11-10
|
|
35
|
+
|
|
36
|
+
- Add controlled `SubjectCardLocatorFields` for card-number or DID/QR entry.
|
|
37
|
+
Number entry distinguishes person/animal and animal taxonomy, including
|
|
38
|
+
species beyond the supplied presets. Hosts provide labels/options and own
|
|
39
|
+
resolution and authorization; the fields select no mode, storage or provider.
|
|
40
|
+
|
|
41
|
+
## 0.3.1 - 2026-11-09
|
|
42
|
+
|
|
43
|
+
- Add a persisted RTC completion signal for local/remote hangup and injected
|
|
44
|
+
canonical terminal-state observation. Release tracks, de-duplicate end
|
|
45
|
+
requests, preserve retryable history failures and cancel invitations after
|
|
46
|
+
connection failure. Load browser media capability before issuing a grant.
|
|
47
|
+
|
|
48
|
+
- Add shared account-level push registration controls with explicit enable,
|
|
49
|
+
current-browser disable, other-device revocation and unavailable/denied
|
|
50
|
+
states. Permission requests, transports, identity and persistence remain in
|
|
51
|
+
the host adapters.
|
|
52
|
+
|
|
53
|
+
- Add one controlled emergency-contact card directory with separate controller
|
|
54
|
+
context, primary-recipient presentation and injected add/remove/priority
|
|
55
|
+
operations. It owns no storage or authority and can render the same state
|
|
56
|
+
across execution modes; native rendering remains a separate adapter.
|
|
57
|
+
|
|
58
|
+
- Specify the complete created-card emergency acceptance journey under the
|
|
59
|
+
existing Tuskr IDs: My card, dependent/controller/contact defaults, pasted
|
|
60
|
+
identifier/manual tuple/camera/image intake, linked-identifier discovery,
|
|
61
|
+
Encounter-scoped contact and RTC, recipient-card history, exceptional access
|
|
62
|
+
and ambulance/hospital handover. Distinguish requirements from executed
|
|
63
|
+
evidence and isolated media cases from full lifecycle acceptance.
|
|
64
|
+
|
|
65
|
+
## 0.3.0 - 2026-11-08
|
|
66
|
+
|
|
67
|
+
- Export shared device-assistance preferences through an independent SOS entry,
|
|
68
|
+
delegating its controlled web renderer to Antifraud 0.3.0. Keep runtime,
|
|
69
|
+
capability detection, storage and authorization in the owning application.
|
|
70
|
+
Native preferences rendering is not implemented by this release.
|
|
71
|
+
- Typecheck, build and the independent export smoke pass. Cross-application
|
|
72
|
+
phone-authenticated browser checks belong to the CH acceptance evidence.
|
|
73
|
+
- List the three implemented runtime exports separately from the acceptance
|
|
74
|
+
catalogue. Base shell/profile/card extraction from the existing domain
|
|
75
|
+
package remains pending; controller administration has a separate owner.
|
|
76
|
+
|
|
77
|
+
- Specify shared subject-control placement, semantic option/action colours,
|
|
78
|
+
account-menu versus subject-device grants, appearance namespace parity and
|
|
79
|
+
separate model enablement/availability/preparation states in the existing
|
|
80
|
+
Tuskr cases. These are acceptance requirements, not new runtime readiness.
|
|
81
|
+
|
|
82
|
+
- Correct the shared acceptance guides to use the selected simulated-phone
|
|
83
|
+
tests without mailbox access. Treat current email-only Organization/employee
|
|
84
|
+
contracts as an implementation gap; preserve official-source verification,
|
|
85
|
+
independent profile authority and existing GW/DID behavior.
|
|
86
|
+
|
|
87
|
+
- Replace the dated developer handoff with numbered, README-linked guides for
|
|
88
|
+
generic portal modes/authentication and detailed cross-portal Tuskr cases.
|
|
89
|
+
Preserve the existing `SOS-PORTAL-001`-`029` and specialist research IDs.
|
|
90
|
+
- Distinguish public Demo real-email account login from fixed Firebase test
|
|
91
|
+
phone fixtures, BFF-owned Demo persistence from Test Network authority/GW
|
|
92
|
+
lifecycle, and dedicated RTC media from Communication history and assistants.
|
|
93
|
+
- Document positive/negative Personal ? Professional journeys, both-side
|
|
94
|
+
readback, profile/relationship revocation, sector variants and evidence
|
|
95
|
+
boundaries without claiming unexecuted gates have passed.
|
|
96
|
+
- Specify dependency-by-case progression: BFF/memory Demo first, independent
|
|
97
|
+
terminology-cache and RTC additions, and memory-GW -> local Fabric ->
|
|
98
|
+
online Test Network acceptance for network cases. Retain green evidence and
|
|
99
|
+
rerun only failed/affected gates while closing the cumulative release set.
|
|
100
|
+
|
|
101
|
+
## 0.2.3 - 2026-11-07
|
|
102
|
+
|
|
103
|
+
- Render caller-cancelled Communications as `Cancelled`/`Cancelada` rather
|
|
104
|
+
than collapsing them into an undefined or generic ended state.
|
|
105
|
+
- Let the host distinguish a caller cancellation from an unanswered timeout
|
|
106
|
+
when ending an RTC session; media teardown remains separate from canonical
|
|
107
|
+
Communication persistence.
|
|
108
|
+
|
|
109
|
+
## 0.2.2 - 2026-11-07
|
|
110
|
+
|
|
111
|
+
- Render the canonical ringing, missed and ended state beside every call
|
|
112
|
+
Communication in the shared Personal/Professional conversation surface.
|
|
113
|
+
Host portals no longer need divergent status labels to expose call history.
|
|
114
|
+
|
|
115
|
+
## 0.2.1 - 2026-11-07
|
|
116
|
+
|
|
117
|
+
- Pin `sos-data-utils-ts@0.6.28`, the exact release that owns the portal RTC
|
|
118
|
+
Communication contract consumed by `createLiveKitRealtimeCallClient`. Clean npm
|
|
119
|
+
installs no longer retain a nested pre-RTC data-utils release.
|
|
120
|
+
|
|
121
|
+
## 0.2.0 - 2026-11-07
|
|
122
|
+
|
|
123
|
+
- Establish this package as the shared presentation boundary consumed directly
|
|
124
|
+
by CH Personal and Professional in every flavour. Product portals provide
|
|
125
|
+
authorization, policy and BFF adapters; UHC compatibility exports no longer
|
|
126
|
+
own the active implementation.
|
|
127
|
+
- Export `SubjectConversationChat` as the single subject-channel renderer over
|
|
128
|
+
canonical Communications. It projects text, governed attachments, clinical
|
|
129
|
+
Bundles, ICS/files, audio and call events without owning persistence,
|
|
130
|
+
signaling or recipient authority.
|
|
131
|
+
- Export `createLiveKitRealtimeCallClient` as a dynamically loaded web RTC adapter
|
|
132
|
+
designed for later Expo substitution. It consumes only the short grant
|
|
133
|
+
issued by the BFF and never receives LiveKit API credentials.
|
|
134
|
+
- Separate CH all-local, telephone-assistant, optional web-assistant and RTC
|
|
135
|
+
integration profiles. Calls use a host-injected dedicated RTC client while
|
|
136
|
+
invitations, terminal events and unanswered audio render as Communications.
|
|
137
|
+
|
|
138
|
+
## 0.1.2 - 2026-11-07
|
|
139
|
+
|
|
140
|
+
- Document and enforce one shared UI contract for Demo, Test Network, web and
|
|
141
|
+
Expo; presentation components never select a persistence adapter.
|
|
142
|
+
|
|
143
|
+
## 0.1.1 - 2026-11-06
|
|
144
|
+
|
|
145
|
+
- Document the GitHub organization handoff, BFF-validated synthetic Demo
|
|
146
|
+
boundary, scoped storage contract and two-browser call verification flow.
|
|
147
|
+
|
|
148
|
+
## 0.1.0 - 2026-11-06
|
|
149
|
+
|
|
150
|
+
- Establish the shared cross-sector portal-component boundary.
|
|
151
|
+
- Publish the initial Tuskr-ready use-case catalogue covering shell, access,
|
|
152
|
+
cards, identity, encounters, communications, appointments, relationships,
|
|
153
|
+
calls, clinical documents, permissions and lifecycle composition.
|
|
154
|
+
- Add the Personal/Professional communications matrix for card-root channels,
|
|
155
|
+
relationship child threads and persisted audio/video call-event states.
|
|
156
|
+
- Keep host/tenant controller governance in Antifraud Hosting and leave
|
|
157
|
+
research/genomics outside the initial core until their package boundary is
|
|
158
|
+
decided.
|
|
159
|
+
- Add the canonical `SubjectConversationChat` React Native/Web adapter over
|
|
160
|
+
Antifraud's neutral conversation surface and SOS subject-conversation
|
|
161
|
+
contracts, including text, governed attachments, FHIR documents and call
|
|
162
|
+
events without moving authorization or delivery into React.
|
|
163
|
+
|