[nk25719]

Summary

• Add one synthetic JSON fixture for each resource currently accepted by the POC.
• Add a separate FHIR R4-shaped Provenance proposal, explicitly outside the current POC resource boundary.
• Document the compact data dictionary, terminology candidates, shared synthetic references, provenance mapping, identifier/reference/version rules, and positive/negative validation matrix.
• Distinguish current JSON/size validation from full FHIR R4/profile/terminology/reference validation.

Review boundaries

• Synthetic-only examples; no real patient data or credentials.
• Does not finalize issue Confirm first use case and minimum dataset #5's proposed use case, the clinical workflow, validator, endpoint, or architecture.
• Issue Use cases Draft #10's four use cases are linked, not duplicated.
• R4/profile and terminology conformance remain to be run after team decisions and selection of validator, terminology release, and reference-resolution strategy.

Closes no issue; this is a review draft for issue #7.