Pick components
Most pilots assume the modeling is the heavy work. For most domains, the components already exist.
Public component libraries on SDCStudio
SDCStudio ships with read-only public libraries that any project can reference directly. The libraries cover the domains most pilots actually care about, plus the standards-anchored ProvGov layer the audit observes. Production deployment is on Google Cloud Run, currently 4.14.13, at sdcstudio.axius-sdc.com.
Domain libraries: what your records are
Pick the one that matches your vertical. These describe the entities your decision flow handles. The libraries compose by slot, so a model can draw on several, and new ones are added as uses for them appear.
NIEM Foundation
1,606 components from the NIEM 6.0 model, Core and six domains
National Information Exchange Model. The federal interoperability vocabulary. State, local, and federal agencies and their downstream consumers already speak this language.
FHIR Clinical
321 components, FHIR R4 clinical resources
If you are in healthcare, your data already needs to map to FHIR. The library makes the mapping a reference, not a translation exercise.
NIH CDE
353 NIH-endorsed Common Data Elements
Research and clinical-trial work where instrument-level standardization matters. Sourced from the NIH portfolio.
Default Library
111 general components
General data structures: people, organizations, transactions, addresses, identifiers, common business entities. The starting point when no vertical library applies cleanly.
SINAN
2,461 components, Brazil's national notifiable-disease system, in Portuguese
Public-health surveillance notifications and investigations, built from the national data dictionaries, with Portuguese labels and descriptions for use in Brazil.
Business Documents
318 components, OASIS UBL 2.3 and GS1 identifiers; header and line records
The buy leg: Order, Order Response, Despatch Advice, Receipt Advice, Invoice, Credit Note and Remittance Advice, each a Governed Data Record that writes and reads the UBL document.
Transport Documents
1,119 components, UBL 2.3 transport documents and UN/CEFACT eCMR
The ship leg: waybill, bill of lading, packing list, manifest, transport status and freight invoice, with the electronic bills of lading as models on the same components.
ISO 20022
1,344 components, payment initiation, interbank transfer, statements and remittance, as minimal records
The pay leg: pain.001 and pain.002, pacs.008 and pacs.002, camt.053 and camt.054, and remt.001, from the ISO 20022 e-Repository.
Traceability (GS1 EPCIS 2.0)
279 components, EPCIS 2.0 events and the Core Business Vocabulary, on the event's own grain
The five EPCIS event types and the FSMA 204 critical tracking events for food traceability, with the CBV lists as coded values.
Peppol
317 components, BIS Billing 3.0 and the ordering profiles
Peppol's Invoice, Credit Note, Order, Order Response and Despatch Advice, composed from the Business Documents components with the BIS rules as assertions.
UN/EDIFACT
83 components, the ISO 9735 interchange and the D.24A qualifier tokens
The interchange envelope as a Governed Data Record and the qualifier codes of ORDERS, ORDRSP, DESADV, RECADV, INVOIC and REMADV; the messages themselves are projections of the Business Documents records.
Imaging
215 components, medical imaging metadata anchored to DICOM tags
The record around an image: dataset, case, visit, study, one series record per modality family with its acquisition parameters by DICOM tag, annotations and the radiology report, chained by the natural keys. Not pixel data.
ProvGov components: what makes the records governable
Domain components describe the entities. The 626 ProvGov components carry the governance evidence the audit actually observes: who did what, when, under what authority, with what classification, with what tamper-evident hash chain. Each family is anchored to a public standard and layers onto your domain model rather than replacing it.
Workflow States
W3C SCXML
Ordered state machines: document lifecycle, record intake, incident response, regulatory filing.
Provenance
W3C PROV-O, Activity Streams 2.0
System identifier, activity type, start and end timestamps, location. Maps to SDC4 AuditType.
Attestation
W3C Verifiable Credentials 2.0
Authority assertion, proof, delegation scope, committed timestamp. Maps to SDC4 AttestationType.
Party and Role
SDC4 PartyType, ParticipationType
Identity, organization, participation function (authorizer, reviewer, subject, provider, processor), mode.
Decision Tables
OMG DMN
Risk score, classification, actor role, severity, legal hold. The condition inputs and outcomes the DMN engine reads.
Retention
W3C DPV
Most-recent + hash, last N records, or full chain. Plus retention justification for regulatory defensibility.
Validation Hashes
SDC4 XdFileType
SHA-256 entity-state-before and entity-state-after hashes. Make the provenance chain tamper-evident.
Access Control Tags
W3C DPV
Public, Internal, Restricted, Confidential classifications, plus consent-required and access-expiry signals.
How the two layers compose
A worked example
A pilot model for a regulated approval flow typically pulls a Party entity from NIEM or Default, an event or encounter from FHIR or NIEM, then layers ProvGov on top: Provenance for who-did-what-when, Attestation for authority, Party and Role for the participation, Decision Table inputs for the rule the flow evaluates, Validation Hashes for tamper evidence, and Access Control Tags for classification. The Receipts the audit produces reference all of it.
Three usage patterns
- Reference: pull a component into your model as-is, no edits. Standards alignment becomes a property of using the right component.
- Copy and Modify: copy a component into your private project and customize it. Use this when a public component is 80% right and you need vertical-specific extensions.
- Create Custom: build from scratch. Reserved for cases where nothing in the libraries fits, which is rarer than most teams assume going in.
The reuse syntax
Components are referenced inside your model using a Markdown-template style. Domain and ProvGov components use the same syntax:
The component is bound to its provenance. Standards compliance is automatic when you compose from standards-aligned components, and the two layers compose cleanly because they were designed to.
What this means for the pilot
For a 30-day audit pilot, this is the difference between "we need to model our domain first" and "we picked four components on Monday and the agent had instances by Tuesday." Most pilots do not need a single custom component to start.
The decision flow you want to audit almost certainly involves entities (people, organizations, transactions, clinical events, claims) that the libraries already cover. Pick the library that matches your vertical, log into SDCStudio, create a private project, and compose the components you need.
Credits reminder
SDCStudio is paid for with credits, bought in advance at 1,000 credits per US dollar. Most pilot projects spend fewer than 20,000 credits ($20 worth) across the full audit period. Buy credits before pointing the agents at your data sources so the introspection step does not stall mid-run.