Platform, configuration and devices · C0832
What happens if someone submits a content type that the system does not recognise?
In the pilot (v0.2.0, synthetic data)
Short answer
The configuration, element type registry and jurisdiction profiles part of the specification (REQ-0101) says the system must accept only content element types that exist in the signed Element Type Registry and must reject and audit any other type. The pilot covers part of this. The rest is designed, not built. Pilot detail: Signed, versioned manifest; push needs two vendor operators; policy changes need dual control. Element Type Registry beyond capabilities not built. Acceptance check: submitting an unregistered type via UI, HL7, FHIR or import returns a coded error, stores nothing, and writes a DENY audit record.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-0101
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- What does the element type registry record about each type of clinical content? Designed
- Who signs each release of the element type registry, and how is it checked before use? Designed
See it in context: Configuration, Element Type Registry and Jurisdiction Profiles · Search the help center · Ask a question