@ampath/esm-dha-workflow-app 4.0.0-claim-workflows.378 → 4.0.0-claim-workflows.379
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/README.md +28 -0
- package/dist/{2473.js → 3196.js} +1 -1
- package/dist/3196.js.map +1 -0
- package/dist/5805.js +1 -1
- package/dist/5805.js.map +1 -1
- package/dist/9049.js +1 -1
- package/dist/esm-dha-workflow-app.js +1 -1
- package/dist/esm-dha-workflow-app.js.buildmanifest.json +30 -30
- package/dist/main.js +1 -1
- package/dist/routes.json +1 -1
- package/package.json +2 -1
- package/src/shr/shr-code-systems.json +363 -0
- package/src/shr/shr-terminology.resource.test.ts +44 -89
- package/src/shr/shr-terminology.resource.ts +45 -115
- package/src/shr/shr-viewer/shr-categories.test.ts +9 -4
- package/src/shr/shr-viewer/shr-categories.ts +7 -7
- package/src/shr/shr-viewer/shr-presentation.test.ts +29 -16
- package/src/shr/shr-viewer/shr-presentation.ts +3 -3
- package/src/shr/shr.resource.ts +1 -8
- package/tools/fetch-shr-code-systems.mjs +135 -0
- package/dist/2473.js.map +0 -1
package/README.md
CHANGED
|
@@ -36,6 +36,34 @@ Keep `HIE_CLIAMS_BASE_URL` in `amrs-integrations/packages/hie-saf/.env` pointed
|
|
|
36
36
|
|
|
37
37
|
Do not commit localhost as the schema `_default` for `hieBaseUrl`.
|
|
38
38
|
|
|
39
|
+
## SHR terminology (`shr-code-systems.json`)
|
|
40
|
+
|
|
41
|
+
The SHR sends many codings bare — a `code` with no `display` (vital-sign LOINC
|
|
42
|
+
codes, body regions, exam findings). Their `coding.system` is a resolvable FHIR
|
|
43
|
+
`CodeSystem` URL, but the browser cannot fetch it: the O3 app shell's
|
|
44
|
+
Content-Security-Policy `connect-src` does not list the SHA FHIR host, so the
|
|
45
|
+
request is blocked before it is sent, and there is no `hie-saf` passthrough
|
|
46
|
+
route for arbitrary terminology.
|
|
47
|
+
|
|
48
|
+
So the concepts ship with the bundle, in
|
|
49
|
+
[`src/shr/shr-code-systems.json`](./src/shr/shr-code-systems.json), keyed by
|
|
50
|
+
CodeSystem **id** (the last path segment) so one copy is correct across UAT and
|
|
51
|
+
production hosts. To refresh it after SHA publishes new codes:
|
|
52
|
+
|
|
53
|
+
```sh
|
|
54
|
+
yarn update-shr-code-systems # defaults to the UAT server
|
|
55
|
+
yarn update-shr-code-systems --server https://host/fhir
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Only the `em-*` systems are taken — the ones the SHR sends bare, and the ones
|
|
59
|
+
whose displays are written for clinicians. The server's other ~110 systems are
|
|
60
|
+
deliberately left out: the big catalogues (diagnoses, interventions, drugs)
|
|
61
|
+
never arrive as bare codings, and several small ones carry displays that are
|
|
62
|
+
worse than humanising the code (`knhts-contact-relationship-cs` maps `parent`
|
|
63
|
+
to lowercase "parent"; `knhts-code-systems-cs` maps `loinc` to the URL
|
|
64
|
+
"http://loinc.org"). A code we don't carry falls back to the raw code, which is
|
|
65
|
+
better than confidently wrong text in a clinical view.
|
|
66
|
+
|
|
39
67
|
## Adapting the code
|
|
40
68
|
|
|
41
69
|
1. Replace all instances of "template" with your frontend module's name
|