@cosyte/synth 0.1.6 → 0.1.7

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## 0.1.7
+
+### Patch Changes
+
+- 65399f9: `@cosyte/synth` now installs beside `@cosyte/deid` 0.2. The `@cosyte/deid` peer range is `^0.1.5 || ^0.2.0`, where it was `^0.1.5`, so npm no longer refuses the install with ERESOLVE when a project already has deid 0.2.3. The tests now run against `@cosyte/deid` 0.2.3, and a new workflow installs the lowest and the highest version the range admits and runs the de-identification loop against each.
+
+  Generated 837P, 837I and 837D claims now write each ICD-10-CM diagnosis code in `HI` without its decimal point (`HI*ABK:J209`, not `HI*ABK:J20.9`), as the 005010 claim guides transmit it. `@cosyte/deid` 0.2 removes a diagnosis code that has a decimal point, which made the X12 pairing loop report clinical codes as scrubbed. The exported `DIAGNOSES` pool (`@cosyte/synth/x12`) holds the same codes in that form: a caller that compared a generated code with `J20.9` must compare with `J209`, or remove the point first.
+
+  Output change: X12. Every generated 837P, 837I and 837D whose diagnosis code has a decimal point, and every X12 corpus that holds one, carries its diagnosis codes without the decimal point; nothing else in them moves. The X12 de-identification loop results move with it and with deid 0.2's X12 pass. An 837 golden file committed from an earlier release has to be regenerated. HL7 v2, FHIR R4 and US Core, C-CDA, NCPDP and ASTM output is byte for byte what it was for the same seed.
+
+- 7bb58a6: Three generated values now follow their standards: the X12 271 benefit percent, the NCPDP Telecom Quantity Dispensed and the ASTM header sender.
+
+  - X12 271: EB-08 (benefit percent) is a decimal fraction, so it is now written as `.8`, `.9` or `1` instead of `80`, `90` or `100`.
+  - NCPDP Telecom: 442-E7 (Quantity Dispensed) carries three implied decimals, so a quantity of 37 is now written as `37000` instead of `37`. It reads back through `@cosyte/ncpdp` as `37.000`.
+  - ASTM: the sender name now sits in H.5 (Sender Name or ID). Before, the sender went to H.3 (Message Control ID) and the analyzer string to H.4 (Access Password). H.3 and H.4 are now empty, and the analyzer string is no longer written to the header. `astmHeaderIdentity` still returns both strings.
+
+  Output change: X12, NCPDP and ASTM. For the same seed, every generated 271, every B1 and B3 Telecom claim, and every ASTM result, order, framed and quirk message changes in the values above, and so do the corpora and de-identification loop results built from them. Every other generated artifact is byte for byte what it was for the same seed. If you commit golden files from an earlier release, regenerate each 271, B1, B3 and ASTM golden file from its seed with this release and commit the new bytes.
+
 ## 0.1.6
 
 ### Patch Changes

package/dist/astm/index.cjs

@@ -666,7 +666,8 @@ function buildResultInput(options) {
     records.push({ type: "C", source: "L", text: rng.pick(ASTM_COMMENT_TEXT), commentType: "G" });
   }
   return {
-    header: { fields: [head.sender, head.analyzer] },
+    // H.3 (message control id) and H.4 (access password) stay empty; H.5 is the sender name.
+    header: { fields: ["", "", head.sender] },
     records,
     terminationCode: "N"
   };