@cosyte/transform 0.0.2 → 0.0.3

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 CHANGED
@@ -14,6 +14,13 @@ its public history at `0.0.x`, per the cosyte version ladder (`0.0.x` until firs
14
14
 
15
15
  ### Added
16
16
 
17
+ - **A brand image at the top of `README.md`.** The page opens with the Cosyte lockup, served as a
18
+ `<picture>` with a light and a dark source so it follows the reader's theme, and carrying alt text
19
+ that describes the mark for anyone reading with images off or a screen reader on. The block is
20
+ copied byte for byte from the `hl7` README, which is the reference the suite mirrors, so the eight
21
+ repos that carry it stay identical rather than drifting into eight hand-typed variants. Nothing
22
+ else on the page moved: the title, the summary blockquote and every code sample are unchanged, and
23
+ no API, issue code, mapping or transformed value differs.
17
24
  - **Phase 6 — terminology value translation of coded fields** (roadmap §Phase 6). Coded fields that
18
25
  earlier phases carried **structurally** (code preserved, system recognized) are now
19
26
  **value-translated** through their IG segment-map `mappedVia` ConceptMaps. Adds a `$translate`-shaped,
@@ -321,6 +328,13 @@ its public history at `0.0.x`, per the cosyte version ladder (`0.0.x` until firs
321
328
 
322
329
  ### Fixed
323
330
 
331
+ - **The README no longer says this package is unpublished.** It is on npm, and the sentence sat a
332
+ few lines above the page's own `npm install` instructions, so the page contradicted itself and a
333
+ reader had no way to tell which half was current. On the npm page it was worse: the same sentence
334
+ rendered directly beneath npm's own header, which shows the version being served. The replacement
335
+ names no version deliberately. A version written into prose is the part that goes stale, and the
336
+ registry is the only thing that knows which one is current.
337
+
324
338
  ### Security
325
339
 
326
340
  [Unreleased]: https://github.com/cosyte/transform/commits/main
package/README.md CHANGED
@@ -1,3 +1,8 @@
1
+ <picture>
2
+ <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
3
+ <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
4
+ </picture>
5
+
1
6
  # @cosyte/transform
2
7
 
3
8
  > HL7 v2 → FHIR R4 transformation for Node.js and TypeScript — **IG-grounded, fail-safe, value-free
@@ -8,7 +13,7 @@ parsers, it is a **consumer**: it takes already-parsed [`@cosyte/hl7`](https://g
8
13
  composites and produces validated [`@cosyte/fhir`](https://github.com/cosyte/fhir) model nodes,
9
14
  grounded on the official **HL7 Version 2 to FHIR** Implementation Guide (`hl7.fhir.uv.v2mappings`).
10
15
 
11
- > **Status:** pre-alpha (`0.0.x`), not yet published to npm. This release ships the
16
+ > **Status:** pre-alpha (`0.0.x`), published to npm. This release ships the
12
17
  > six safety-critical datatype converters and the value-free diagnostic channel, the
13
18
  > message-level assembly, HL7 v2 **ADT → FHIR Patient + Encounter**, the **ORU^R01 → FHIR
14
19
  > DiagnosticReport + Observation** results graph, the order-entry graph — **ORM_O01 /
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cosyte/transform",
3
- "version": "0.0.2",
3
+ "version": "0.0.3",
4
4
  "description": "HL7 v2 → FHIR R4 transformation library for Node.js and TypeScript — IG-grounded, fail-safe, value-free diagnostics; never a confident wrong FHIR value.",
5
5
  "keywords": [
6
6
  "hl7",