Why ART-DECOR® matters for standards work

ART-DECOR®

Anyone who has worked on a national or international specification knows the failure mode: a Word document describes the intended constraints, a spreadsheet lists the value sets, an example file shows what a message should look like, and a separate Schematron tries to check conformance. Six months later, none of them quite agree with each other.

ART-DECOR® exists to remove that gap. It is an open framework and methodology for authoring and maintaining the artefacts that make up a healthcare specification — data sets, templates, value sets, scenarios and business rules — in one governed, computable place.

A single source of truth

Instead of prose that humans must interpret, ART-DECOR captures constraints as structured, machine-readable definitions. The narrative implementation guide, the example instances and the validation artefacts are then generated from that single model, so they cannot silently drift apart. When a constraint changes, everything downstream changes with it.

From specification to computable artefacts

Because the model is computable, it can produce what implementers actually need: HL7 CDA and FHIR templates, value sets bound to the right code systems, Schematron for validation, and worked examples. That shortens the distance between "the committee agreed on X" and "a vendor can build and test X."

Governance and reuse

Standards work is rarely a one-off. Templates and value sets defined once should be reusable across projects and versions, with a clear history of what changed and why. ART-DECOR treats governance — versioning, review status, reuse across projects — as a first-class concern rather than an afterthought, which is exactly what long-lived national programmes require.

Where it fits in a project

In practice we use ART-DECOR from the first modelling workshops through to conformance testing: to agree the data set with clinical experts, to publish an implementation guide stakeholders can read, and to hand developers artefacts they can validate against. The result is fewer surprises late in the project, when they are most expensive.

If you are starting a specification and expect to maintain it for years, the question is less "should we use tooling like this?" and more "how much rework will we accept if we don't?"

Back to all posts Discuss a project