Runnable end-to-end starters for the
@cosyte/*healthcare libraries, on synthetic data only.
Runnable end-to-end starters for the @cosyte/* healthcare libraries. Each starter is a small,
complete program you can clone, install, and run in a minute. Every message, document, and image
here is synthetic: generated by @cosyte/synth or written by hand for the example. None of it is
real patient data.
- Why this exists
- Status
- Starters
- Run a starter
- Layout
- Versions and CI
- Documentation
- Support
- Security
- Contributing
- License
A library's reference tells you what each function does; a starter shows several of them working together in a complete program you can run. Each starter here is small enough to read in one sitting, runs with no build step, no database, and no network beyond localhost, and asserts its own key output in its tests, so you can clone one and build on it.
Ten starters, listed below. Each sets its @cosyte/* versions in its own package.json and commits
its package-lock.json, and CI runs every one of them on Node 22 and 24. This repository ships no
package: there is no root package.json, no changeset, and no CHANGELOG.md. A version tag releases
the starters' pages for docs.cosyte.com.
| Starter | Libraries | What it shows | Run |
|---|---|---|---|
| hl7-mllp-listener | @cosyte/mllp, @cosyte/hl7, @cosyte/synth |
An MLLP listener that parses each ADT^A01 it receives, prints a summary, and answers with an ACK; a client sends it a synthetic message | cd hl7-mllp-listener && npm install && npm start |
| hl7-to-fhir | @cosyte/transform, @cosyte/fhir, @cosyte/hl7, @cosyte/synth |
An ADT^A01 converted to a FHIR R4 message Bundle (Patient, Encounter, MessageHeader), each resource then validated | cd hl7-to-fhir && npm install && npm start |
| x12-eligibility | @cosyte/x12, @cosyte/synth |
A 271 eligibility response read into payer, subscriber, coverage status, and benefit lines, then the 270 inquiry it answers, built and matched by its trace | cd x12-eligibility && npm install && npm start |
| x12-remittance | @cosyte/x12, @cosyte/synth |
An 835 remittance summarized: the payment; each claim's status, amounts, and adjustment reasons; and the balance check | cd x12-remittance && npm install && npm start |
| ncpdp-claim | @cosyte/ncpdp, @cosyte/synth |
An NCPDP Telecom B1 claim and a paid response, parsed into routing, product, pricing, and the payer's answer | cd ncpdp-claim && npm install && npm start |
| astm-lab-results | @cosyte/astm, @cosyte/synth |
An analyzer upload (ASTM E1394 records in E1381 frames) decoded, checksums checked, into a results table | cd astm-lab-results && npm install && npm start |
| dicom-metadata | @cosyte/dicom, @cosyte/deid |
DICOM Part 10 metadata read from a synthetic file, then the header de-identified with a value-free manifest | cd dicom-metadata && npm install && npm start |
| ccda-summary | @cosyte/ccda, @cosyte/synth |
A C-CDA document parsed into problems, medications, and allergies | cd ccda-summary && npm install && npm start |
| deid-hl7 | @cosyte/deid, @cosyte/hl7, @cosyte/synth |
An HL7 v2 admit message run through the Safe Harbor policy, the value-free manifest of what it removed or generalized, and the positions it passed through unexamined | cd deid-hl7 && npm install && npm start |
| cli-tour | @cosyte/cli, @cosyte/hl7, @cosyte/synth |
The cosyte command over a synthetic HL7 v2 message: parse, inspect, validate, convert to a FHIR R4 Bundle, and de-identify |
cd cli-tour && npm install && npm start |
git clone https://github.com/cosyte/examples.git
cd examples/deid-hl7
npm install
npm start
npm testEach starter needs Node 22 or later and nothing else: no build step, no database, no network beyond
localhost. npm start runs it and prints what it did. npm test runs it again and asserts the key
output. Each starter's README shows the expected output and walks through the code.
npm ci installs exactly the versions in the starter's committed package-lock.json. The ranges in
its package.json are carets, such as ^0.1.0, and every @cosyte/* library is below 1.0: below
1.0 a breaking change can ship in a patch release, so a caret range does not protect you. When you
take a starter into your own project, pin each library to an exact version:
npm install --save-exact @cosyte/hl7@0.1.8What a starter prints is safe to log: types, codes, counts, lengths, and positions, never a value that identifies a person. What is safe to log lists it.
Each top-level folder with a tracked package.json is one starter and its own npm project: a
committed package-lock.json, src/, test/, and a README. There is nothing to install at the
root. A starter's integration tests live in test/integration/, tagged by file name:
*.fast.test.js run in npm test, *.full.test.js only in npm run test:full. They call the
libraries' public APIs only.
docs-content/ holds the docs site's pages: an overview that routes by what you want to build, one
page per starter, and the guides around them. Each starter page's expected output and code are
generated from the starter by scripts/docs-content.mjs, and CI fails when a starter has no page or
a page no longer matches its starter.
Each starter sets its @cosyte/* versions in its own package.json and commits its
package-lock.json. CI installs every starter from its lockfile and runs npm test on Node 22 and
24, on every pull request and every push to main; npm test includes each starter's fast
integration tests, which chain the libraries through their public APIs. The full integration suite,
npm run test:full in every starter with its seed sweeps, runs nightly on main, and a library's
release can run it against the package it is about to publish. Changes reach main only through pull requests
that pass All starters (every starter on both Node lines) and no-emdash.
The starters are documented at docs.cosyte.com/examples: pick one by what you want to build, then read what it shows, how to run it, and its code. The libraries themselves live in their own repositories and are documented at docs.cosyte.com. Each starter's own README shows its expected output and walks through its code.
Questions and bug reports start on the issue tracker.
Need it built, or hosted and run for you? Talk to us.
Report a vulnerability privately, as the security policy describes, never in a public issue.
Synthetic data only. Every message, document, and image here is generated by @cosyte/synth or
written by hand, and must not pass for a real record. Real patient data never enters this
repository, a fixture, or a log.
A starter exists to be cloned and built on, so every pattern in it is meant to be safe to copy. The
MLLP listener in hl7-mllp-listener binds 127.0.0.1 only, and no starter reaches the network
beyond localhost. What you build from a starter, and the data you run through it, are yours to
secure: transport, storage, access control, and what reaches your logs.
The organization's contributing guide and code of conduct apply here. AGENTS.md holds what is specific to this repository: the build, the tests, and the gate to run before you push. A starter's README says only what its starter runs and its test asserts. A new starter is tested from the pull request that adds it, with no workflow edit.
MIT, Copyright (c) 2026 Cosyte LLC. See LICENSE.
Built by Cosyte.