@cosyte/transform 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.1
+
+### Patch Changes
+
+- 791d994: Published through npm trusted publishing, with provenance.
+
+  The code, API and behavior are unchanged from 0.1.0. Only the README differs.
+
 ## 0.1.0
 
 ### Minor Changes
@@ -241,7 +249,7 @@
 
 - 9fd8f24: The npm `description` no longer carries an em dash (`EMDASH-CONFORMANCE`).
 
-  The brand rule bans U+2014 on every cosyte surface, and this string is the most visible one the
+  The brand rule bans U+2014 on every Cosyte surface, and this string is the most visible one the
   package has: it is the subtitle on the npm package page and the one line shown in every npm search
   result. It now reads with a colon, which is what the rule's own remedy list names first.
 
@@ -292,7 +300,7 @@ shipped, and the empty section stubs that existed to receive the next hand-writt
 
 The entries below follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the generated
 sections above use the format Changesets writes, which is a version heading and a list of the
-changes that release consumed. Versions follow the cosyte pre-alpha ladder, `0.0.x` until first
+changes that release consumed. Versions follow the Cosyte pre-alpha ladder, `0.0.x` until first
 alpha, rather than [Semantic Versioning](https://semver.org/spec/v2.0.0.html) alone.
 
 ### Fixed

package/README.md

@@ -7,10 +7,10 @@
 
 # @cosyte/transform
 
-> HL7 v2 → FHIR R4 transformation for Node.js and TypeScript: **IG-grounded, fail-safe, value-free
-> diagnostics; never a confident wrong FHIR value**.
+> HL7 v2 → FHIR R4 transformation for Node.js and TypeScript: **IG-grounded, with value-free
+> diagnostics**.
 
-`@cosyte/transform` is the healthcare **transformation** layer of the cosyte suite. Unlike the
+`@cosyte/transform` is the healthcare **transformation** layer of the Cosyte suite. Unlike the
 parsers, it is a **consumer**: it takes already-parsed [`@cosyte/hl7`](https://github.com/cosyte/hl7)
 composites and produces validated [`@cosyte/fhir`](https://github.com/cosyte/fhir) model nodes,
 grounded on the official **HL7 Version 2 to FHIR** Implementation Guide (`hl7.fhir.uv.v2mappings`).
@@ -33,10 +33,9 @@ that is clean against R4 plus those profiles, and it lists every finding. The su
 > OML_O21 → ServiceRequest** and **RXO → MedicationRequest**), the thin IG singles
 > (**VXU_V04 → Immunization**, **SIU_S12 → Appointment**, **MDM_T02 → DocumentReference**), all
 > via `toFhir(msg)`, and **terminology value translation** of coded fields: route/site,
-> appointment type, order priority, and substitution are now value-translated through their IG
+> appointment type, order priority, and substitution are value-translated through their IG
 > `mappedVia` ConceptMaps via `toFhirCodeableConceptVia`, fail-safe on any code the IG leaves unmapped.
-> The v2→FHIR direction is feature-complete for the IG-covered message set. It also ships a
-> **narrow reverse path**, FHIR → v2: `toV2Patient(patient, trigger)` and
+> It also ships a **narrow reverse path**, FHIR → v2: `toV2Patient(patient, trigger)` and
 > `toV2Observation(observation, trigger)` emit a complete v2 message carrying a `PID` or an `OBX`.
 > Deeper terminology, profiles, and any wider FHIR → v2 conversion are not implemented.
 
@@ -191,8 +190,7 @@ number is reproducible against a pin rather than against whatever was current; `
 regenerates it, and the test suite fails when the published result and a live run disagree.
 
 **And silence is not completeness.** Every segment occurrence that contributed nothing to a resource
-in the returned bundle raises one value-free issue naming it, so you can read the issues list instead
-of diffing the message against the bundle: `TRANSFORM_SEGMENT_NOT_EMITTED` when the IG publishes a
+in the returned bundle raises one value-free issue naming it: `TRANSFORM_SEGMENT_NOT_EMITTED` when the IG publishes a
 segment map for that name (a gap here), `TRANSFORM_SEGMENT_NO_IG_MAP` when it publishes none, or when
 the name could not be classified at all (a gap in the standard, or a damaged line). The location is
 `DG1[2]` for a name that passes the v2 segment-identifier shape, 1-based among that name's

package/dist/index.cjs

@@ -5108,7 +5108,7 @@ function toV2Observation(resource, trigger, options = {}) {
 }
 
 // src/index.ts
-var VERSION = "0.1.0";
+var VERSION = "0.1.1";
 
 exports.ADDRESS_TYPE_MAP = ADDRESS_TYPE_MAP;
 exports.ADDRESS_USE_MAP = ADDRESS_USE_MAP;