Standards

Healthcare data standards, one library each.

HL7 v2, FHIR, C-CDA, X12, NCPDP, ASTM, DICOM and MLLP each have a parser; clinical terminology and de-identification each have an engine. Every page says what the standard is and where it shows up, with sources, then what our library does, what it does not do, and what else you could use.

Need it integrated? Talk to us.

The pages

Pick the standard on your wire.

@cosyte/hl7

HL7 v2

The pipe-delimited messages hospital systems exchange for admissions, orders and results.

@cosyte/fhir

FHIR

The resource-based API standard that certified EHRs and many US payers must expose.

@cosyte/ccda

C-CDA

The XML clinical documents behind transitions of care, referrals and discharge summaries.

@cosyte/x12

X12

The HIPAA EDI transactions behind claims, remittance, eligibility and enrollment.

@cosyte/ncpdp

NCPDP

Pharmacy claims in the Telecommunication Standard, and ePrescribing in SCRIPT.

@cosyte/astm

ASTM

The framing and record formats lab analyzers use to send results to a laboratory information system.

@cosyte/dicom

DICOM

The standard and file format behind medical imaging, from CT to ultrasound.

@cosyte/mllp

MLLP

The TCP framing HL7 v2 feeds travel in, with acknowledgements on top.

@cosyte/terminology

Terminology

LOINC, SNOMED CT, RxNorm, ICD-10-CM and UCUM: the code systems every other standard points into.

@cosyte/deid

De-identification

HIPAA Safe Harbor and Expert Determination, applied to parsed healthcare data.

Across the standards

Libraries that work across several of them.

  • @cosyte/transformMaps parsed HL7 v2 messages to FHIR R4 resources, following HL7's v2-to-FHIR implementation guide.
  • @cosyte/synthDeterministic synthetic fixtures for six formats, each built through its parser's own serializer, so tests never need real patient data.
  • @cosyte/cliThe parsers from a terminal, and the same commands as tools for an agent over MCP.

Install the library, or hand us the integration.

Every library is free and MIT-licensed. If you would rather have the integration built and run for you, that is what we sell.