Pattern Co-Usage Map
Common, effective combinations of patterns for rapid delivery.
Overview
Use these as recipes for project setup.
Pattern Usage by Scenario
The following diagrams show how patterns work together in specific healthcare workflow scenarios:
Rapid IG Bootstrap (2 weeks)
Walking skeleton with HL7 auto-build preview and validator gate; enough terminology to demo interoperability.
Terminology-First Approach
When semantic alignment is primary risk, start with terminology service gates and pinned content versions.
Common Pattern Combinations
Rapid IG bootstrap (2 weeks)
Purpose: Walking skeleton with HL7 auto-build preview and validator gate; enough terminology to demo interoperability.
Pattern Combination:
- Thin-Slice Use-Case First - Prevent profile-first paralysis by starting with a thin slic...
- Executable Contract Backlog - Make requirements testable using conformance statements + ex...
- FSH-First, Repo-First Authoring - Use FSH + Git for diffable, distributed authoring; avoid han...
- HL7 Build Preview Pipeline (base template) - Use HL7 auto-build to generate previews for every push using...
- Example-Driven Profiling - Use examples as first-class design artifacts; every profile/...
- Validator Gate in CI - Run IG Publisher validation as a hard gate on every PR....
Key Interactions:
- PL-01 defines the first thin slice and examples that drive all subsequent authoring work
- PL-06 keeps artifacts diffable in Git so reviews and governance can move quickly
- PL-08 ensures every push produces a hosted preview and shared build logs
- PL-14 keeps profiles grounded in executable examples
- PL-15 makes validation failures immediate and non-negotiable
Terminology-first for high semantic risk
Purpose: When semantic alignment is primary risk, start with terminology service gates and pinned content versions.
Pattern Combination:
- Three-Layer Terminology Model - Separate CodeSystem/ValueSet/ConceptMap roles to reduce sema...
- Terminology as a Service (TaaS) Gate - Run $expand/$validate-code/$lookup in CI against a pinned te...
- Terminology Release Train - Coordinate terminology change with IG releases using depreca...
- Cross-Product Interop Matrix - Test across validators/servers/SDKs continuously to catch ec...
Key Interactions:
- PL-09 establishes stable CodeSystem/ValueSet/ConceptMap roles before profiling expands
- PL-10 turns terminology operations ($expand/$validate-code) into CI gates
- PL-11 synchronizes terminology changes with IG package releases
- PL-16 detects ecosystem variance early by running the same test vectors across products
Pattern Synergies
The patterns in this collection are designed to work together. Start with a core pattern like Broker or Security Strategy, then add complementary patterns as needed.
Customization
These combinations are starting points. Adapt them based on your specific requirements, existing infrastructure, and organizational constraints.