@cosyte/hl7
ComingHL7 v2
cosyte
We build and maintain an MIT-licensed suite of parsers for the formats that carry clinical data — HL7 v2, MLLP, DICOM, X12, C-CDA, NCPDP, and FHIR. Each one is a lenient reader that never silently drops a field, a spec-clean emitter, and a dependency footprint small enough to audit in an afternoon. We also consult on the integrations that put them to work.
import { parse } from '@cosyte/hl7';
// A synthetic ADT^A01 admit — invented identifiers, never real PHI.
const raw = [
'MSH|^~\\&|SENDING|HOSP|RECEIVING|HOSP|20260701120000||ADT^A01|MSG0001|P|2.5.1',
'EVN|A01|20260701120000',
'PID|1||900000001^^^HOSP^MR||DOE^JANE^Q||19850101|F',
'PV1|1|I|WEST^305^1^HOSP',
].join('\r');
// Lenient reader: warns on a real-world quirk, never silently drops a field.
const msg = parse(raw);
const mrn = msg.segment('PID').field(3).component(1); // '900000001'
for (const w of msg.warnings) console.warn(w.code, w.path); The suite
The list is the proof. Each package is engineered to the same standard-conformance bar and ships under MIT.
@cosyte/hl7
ComingHL7 v2
@cosyte/mllp
ComingMLLP
@cosyte/dicom
ComingDICOM Part 10
@cosyte/x12
ComingASC X12 / HIPAA 005010
@cosyte/ccda
ComingHL7 C-CDA R2.1
@cosyte/ncpdp
ComingNCPDP SCRIPT + Telecom
@cosyte/fhir
ComingHL7 FHIR
Consulting
We work with US labs, providers, and health-tech vendors on the integration work that has to be right the first time — ingesting an HL7 v2 feed, fielding 270/271 eligibility, posting an 835 remittance, parsing a C-CDA on referral, reading a DICOM study, handling a Surescripts ePrescribing message.
The credibility comes from the open-source suite. The engagement comes from the same engineering — quiet, spec-grounded, and honest about what is and is not solved.
Who we are
cosyte is a solo company. The same person who writes the parsers takes the calls and ships the engagements. No sales floor, no out-of-date marketing site, no “platform” pitch over a hollow stack. The site you're reading and the code on GitHub are the company.
Tell us what's on the wire and what has to come out the other side. We read the spec, write the code, and stay honest about what's solved.