NEWS

---

r4subcore 0.3.0

• Add evidence_diff(), which compares two evidence tables and reports what changed between them: which findings were added, removed, or changed, and whether each change made the submission better or worse. Rows are matched on the indicator and asset, duplicate keys collapse to the worst row, and the result is ordered with regressions first so a team sees what to act on. This turns the evidence table into something you can track run over run, and it is the raw material behind higher-level trend views such as sci_diff().

r4subcore 0.2.1

• hash_id() now hashes in memory with rlang::hash() instead of writing a temporary file and calling tools::md5sum on every call. The result is the same shape (a 32-character hex string, deterministic) but roughly three orders of magnitude faster, which removes the main bottleneck when building a trace model or generating identifiers for a large submission. The exact hash values change; they are opaque identifiers, not a persisted contract.
• Add check_define_consistency() and define_variables(). The first compares the variables declared in Define-XML against the variables actually present in the datasets and emits evidence for each: a match, a variable documented but absent from the data, or a variable present but not documented. Drift between Define-XML and the data is a common submission problem, and this makes it a scored quality indicator. The second extracts the dataset and variable pairs from a Define-XML file.

r4subcore 0.2.0

• Add read_p21_report(), which loads a Pinnacle 21 validation report from disk (CSV natively, Excel through the optional readxl package) ready for p21_to_evidence(). A team can now go from the report Pinnacle 21 already produces to scored evidence without hand-building a table.
• canon_severity() now recognizes "notice", the severity Pinnacle 21 uses for its lowest level, mapping it onto info.
• The evidence table now carries a schema version. as_evidence() stamps it, evidence_schema_version() reports the current version or the version of a given table, and migrate_evidence() upgrades a table written by an older release. validate_evidence() tolerates an unstamped table but refuses an unknown or newer version, so a table written by a future release cannot be silently mis-scored.
• Fix import_evidence(): a CSV or JSON round-trip could leave an all-NA character column (for example source_version) typed as logical, which then failed validation. Every schema column is now coerced back to its declared type on import.
• Add evidence_schema_spec(), which publishes the evidence schema as a tidy table (column, type, required, allowed values, description) for use as a data dictionary or reference.
• Add vignette: "The R4SUB Evidence Schema", the formal specification of the evidence table shared across the ecosystem.
• Add adrg_to_evidence() and adrg_sections() for Analysis Data Reviewer's Guide coverage. Given a structured summary of which standard ADRG sections a guide contains, this emits usability evidence: missing required sections fail, missing recommended sections warn. The same machinery covers the SDRG via source_name.
• Add evidence_sources(), a reference table of supported and planned evidence sources with their format, pillar, and entry point.
• Harden define_xml_to_evidence() for real-world Define-XML variability. It now matches elements by local name, so it reads files regardless of how they mix the ODM and def: namespaces (a plain //ItemGroupDef query silently missed namespace-prefixed elements). Derivations are resolved from a referenced MethodDef when the Origin carries no inline text, missing optional elements are tolerated, and a partially parseable file now returns an informative warning.
• Clarified the package DESCRIPTION: "R4SUB" expands to "Ready for Submission" (previously "R for Regulatory Submission", inconsistent with the rest of the ecosystem).

r4subcore 0.1.2

• define_xml_to_evidence(): Parse Define-XML 2.0/2.1 files into evidence, emitting Q-DEFINE-001 (dataset present), Q-DEFINE-002 (variable documented), and Q-DEFINE-003 (derivation present) indicators.
• export_evidence() / import_evidence(): Save and reload validated evidence tables in CSV, RDS, or JSON format with metadata attributes.

r4subcore 0.1.1

• Added ORCID for package author in Authors@R.
• Added r4subdata to Suggests — the companion example-data package is now on CRAN.

r4subcore 0.1.0 (2026-02-20)

• Initial CRAN release.