Public on SDCStudio · nineteen libraries · free to reuse
The component libraries are the standards your partners already exchange, published as governed components on SDCStudio: NIEM, HL7 FHIR, NIH Common Data Elements, OASIS UBL, ISO 20022, GS1 EPCIS, XBRL Global Ledger, FOCUS and eleven more. A model composes them by reference instead of rebuilding them. The standard's meaning is bound to each component, so a record made from them carries it, and two organizations that compose the same component mean the same thing without a mapping table between them.
Two ways in
If you sign for data exchange
Every partner that adopts a standard reads it a little differently, and every pair of partners pays to reconcile the difference, again at every version. A library component is the interpretation, written down once: its definition, its allowed values, its links to the standard, reviewed and published. A partner that composes it is not reading the standard again; it is using the same component.
Reusing a published component is free. Your models compose the libraries and add only what is yours: the records only your organization keeps.
See it on your own data: the 30-Day AuditIf you build models
Each component has a stable library slot, a URI that resolves to the published component in any project. A model names the slot, and the component is reused as published: the Default library's address, a UBL party, an ISO 4217 currency. A published component never changes; a correction is a successor with its lineage recorded.
Where a library ships default vocabularies (customer status, account type, employment type), they are yours to copy, edit and swap into your own copy of the record. Where the values are a standard's own (FOCUS charge categories, SINAN codes), they are written exactly as the standard writes them.
The libraries in the documentationThe libraries
Public component counts measured on production 19 October 2026; the public catalog API gives today's count for any library by its project name.
NIEM · 1,603 components
The National Information Exchange Model: justice, public safety, emergency management, immigration.
FHIR · 321 components
HL7 FHIR clinical resources.
NIH CDE · 353 components
NIH Common Data Elements for clinical research.
NIH PhenX · 28 components
A PhenX Toolkit instrument (180701) as a record.
SINAN · 2,459 components
Brazil's notifiable-disease surveillance forms, in Portuguese. The codes
Imaging · 213 components
Imaging study, series and instance records anchored on DICOM.
Business Documents · 346 components
OASIS UBL business documents as header and line records, Request for Quotation through Remittance Advice.
Peppol · 317 components
Peppol BIS profiles as models over the business documents.
UN/EDIFACT · 81 components
The interchange record and the D.24A qualifier codes.
Transport Documents · 1,119 components
UBL transport documents, eCMR, the DCSA electronic bill of lading, the FIATA eFBL.
Traceability · 277 components
GS1 EPCIS 2.0 events for supply-chain traceability.
ISO 20022 · 1,342 components
Payment and financial messages as records.
CRM · 116 components
Customer relationships: account, contact, lead, opportunity, activity, case, campaign, and consent on the W3C Data Privacy Vocabulary. Vocabularies
ERP · 102 components
Master data: customer, supplier, item, price list, location, inventory balance, employee, on the Open Applications Group's nouns. Vocabularies
Ledger · 29 components
The chart of accounts, the journal entry and its lines, on XBRL Global Ledger. Vocabularies
Human Resources · 190 components
Units, jobs, positions and the employment history as records, on HR Open Standards 4.5 by reference. Vocabularies
FOCUS · 189 components
Cloud, SaaS and AI cost, usage and billing on the FinOps Open Cost and Usage Specification 1.4. A correction is a new record, so the charge history is never overwritten. Vocabularies
Default · 111 components
The domain-agnostic components every other library composes from: names, addresses, identifiers, dates, amounts, consent.
ProvGov · 626 components
Provenance and governance on W3C PROV: who did what, when, under what authority. The components that make any record governable.
How they are built
Each library is built by code from what its standard publishes: the schemas, the code lists, the column definitions. Each component is linked to the part of the standard it comes from, and every component passes a human review before it loads. The standard's license is honored: what may be adapted is adapted with its attribution, and what may only be cited is cited, not reproduced.
Every enumerated value names its definition by IRI. Where the standard publishes its own, the component points there; where it does not, the definition is on a public page, one anchor per value, so a value's meaning can be checked by anyone, outside the catalog.
The libraries are components of the Semantic Data Charter, an open specification. Its reference model is W3C XSD 1.1, and every record made from these components validates against an open schema.
Pick the library that matches your work, compose your records from it in SDCStudio, and keep only what is yours to model. The 30-Day Audit does it with you on one decision flow of your own.