Register Types
FERIN defines five register types based on capabilities. Choose the type that matches your needs—no more, no less.
Capability-Based Conformance
Unlike the 2015 edition's hierarchical model (Core → Extended → Hierarchical), the 2025 edition uses capability-based conformance:
- Each register type provides specific capabilities
- You claim conformance to the type(s) you implement
- Types can be combined based on needs
- There's no "highest" level—just the right fit
The Five Register Types
Content Register
Basic register with content management
Capabilities
- Store and retrieve register items
- Assign and manage identifiers
- Track basic status (valid/invalid, published/unpublished)
- Support required actions (add, invalidate, supersede)
Best For
Simple code lists, reference data, and lookup tables where governance is minimal and content doesn't change frequently.
Concept Register
Content + concept plane modeling
Capabilities (extends Content)
- Model concepts and concept versions
- Link register items to concepts
- Track concept definitions and their evolution
- Support concept relations (specialization, etc.)
Best For
Registers where the meaning of items matters as much as the data, or where definitions evolve over time.
Governed Content Register
Content + formal governance
Capabilities (extends Content)
- Formal proposal and approval workflows
- Role-based access control
- Audit trails for all changes
- Appeal process for disputed decisions
Best For
Registers that require accountability, transparency, or regulatory compliance—where you need to prove who approved what and when.
Governed Concept Register
Concept + governance capabilities
Capabilities (extends Concept)
- All Concept Register capabilities
- Formal governance for concepts and content
- Approval workflows for concept changes
- Concept-level audit trails
Best For
Enterprise terminology or taxonomy management where both meaning and content require formal governance.
Complete Concept Register (CCR)
All capabilities: concept + governance + commitments
Capabilities (extends all)
- All Governed Concept Register capabilities
- Full commitment implementation
- Access commitments (metadata, content, historic)
- Persistence commitments (identifier, content, historic)
- Transparency commitments (full visibility)
Best For
National or international reference registers, standards bodies, and any register that serves as a definitive, citable source.
Choosing a Register Type
Use this decision tree to select the right type:
Quick Selection Table
| Use Case | Recommended Type | Rationale |
|---|---|---|
| Internal code list | Content Register | Simple needs, no external users |
| Product taxonomy | Concept Register | Definitions matter, governance optional |
| Regulatory compliance data | Governed Content Register | Audit trail critical |
| Enterprise data governance | Governed Concept Register | Both meaning and process matter |
| National/international standard | CCR | Full trust and persistence required |
Can I Mix Types?
The capability model is designed to be combinable:
- Yes: You can implement capabilities from multiple types if your use case requires it
- Claim carefully: Only claim conformance to types whose full capability set you implement
- Document deviations: If you implement partial capabilities, document what's included and excluded
Conformance Testing
How do you verify conformance when requirements are capability-based?
Testing Approach
- Identify claimed type(s): What conformance class(es) does your register claim?
- Map to capabilities: Each type has required capabilities
- Test each capability: Verify the capability is implemented and functional
- Document evidence: Provide examples, screenshots, or API demonstrations
Self-Assessment Checklist
Content Register
- ☐ Can add new register items
- ☐ Can assign unique identifiers
- ☐ Can invalidate items
- ☐ Can supersede items
- ☐ Can track valid/invalid status
- ☐ Can track published/unpublished status
Concept Register
- ☐ Can define concepts
- ☐ Can version concept definitions
- ☐ Can link items to concepts
- ☐ Can define concept relations
Governance
- ☐ Can submit proposals
- ☐ Can review and approve/reject proposals
- ☐ Can assign roles
- ☐ Can appeal decisions
- ☐ Maintains audit trail