subscription-service / profiles

Vendor profiles.

A profile is a YAML manifest, a set of StructureMaps, sample test messages, and a regression suite. Drop one into /plugins/profiles/ and the engine knows how to handle that vendor's quirks. All seeded profiles are Apache 2.0 and live in the subscription-service-profiles repository — this catalog is regenerated from those manifests on every site build.

athenahealth

athenaOne 21.x

id: athena v2026-Q2.0

Supported message types: athena-changed-patients, fhir-r4-observation
Quirks handled (3): athena-patient-id-namespace
athena-encounter-departmentid-required
fhir-observation-missing-category-strategy
License: Apache 2.0

View on GitHub → Get the latest release →

Oracle Health (Cerner)

Millennium 2025.x

id: cerner vmillennium-2025.1.0

Supported message types: ADT^A04, ORU^R01
Quirks handled (3): msh3-format
empty-pid-strategy
attachment-encoding
License: Apache 2.0

View on GitHub → Get the latest release →

Epic Systems

Epic 2024.x

id: epic v2024.1.0

Supported message types: ADT^A04, ORM^O01, ORU^R01
Quirks handled (3): msh3-format
empty-pid-strategy
attachment-encoding
License: Apache 2.0

View on GitHub → Get the latest release →

Meditech

Expanse 2025.x

id: meditech vexpanse-2025.1.0

Supported message types: ADT^A04, ADT^A08
Quirks handled (3): msh3-format
empty-pid-strategy
attachment-encoding
License: Apache 2.0

View on GitHub → Get the latest release →

NextGen Healthcare

Enterprise 2025.x

id: nextgen venterprise-2025.1.0

Supported message types: ADT^A04
Quirks handled (3): msh3-format
empty-pid-strategy
attachment-encoding
License: Apache 2.0

View on GitHub → Get the latest release →

Need a vendor we don't list?

Profiles are designed to be community-authored. Fork the community-template, fill in your StructureMaps, and open a PR — or run your profile privately by dropping it into your engine's plugin directory.

If you need a certified profile with a regression suite and an indemnity statement, that ships in the Pro tier.