# r4sub

**r4sub** is the meta-package for the R4SUB (R for Regulatory Submission) clinical submission readiness ecosystem.

A single `library(r4sub)` call installs and attaches all core packages.

## Installation

```r
install.packages("r4sub")
```

## Usage

```r
library(r4sub)
# -- Attaching R4SUB packages (r4sub 0.1.0) -----
#   r4subcore    0.1.1
#   r4subtrace   0.1.0
#   r4subscore   0.1.0
#   r4subrisk    0.1.0
#   r4subdata    0.1.1
#   r4subprofile 0.1.0

# All ecosystem functions are now available
data(evidence_pharma)                                    # from r4subdata
scores <- compute_indicator_scores(evidence_pharma)      # from r4subscore
sci    <- compute_sci(compute_pillar_scores(scores))     # from r4subscore

# Ecosystem utilities
r4sub_packages()   # versions and attachment status
r4sub_status()     # installation check
r4sub_conflicts()  # detect function name collisions
r4sub_news()       # what changed in each package
r4sub_cite()       # citation info for regulatory documents
```

## Suppress startup message

```r
options(r4sub.quiet = TRUE)
library(r4sub)
```

## Packages

| Package | Purpose | Auto-attached? |
|---|---|---|
| **r4subcore** | Evidence schema, scoring primitives, parsers | Yes |
| **r4subtrace** | ADaM/SDTM traceability engine | Yes |
| **r4subscore** | Submission Confidence Index (SCI) scoring | Yes |
| **r4subrisk** | FMEA-based risk quantification | Yes |
| **r4subdata** | Example datasets for demos and testing | Yes |
| **r4subprofile** | Regulatory submission profiles | Yes |
| **r4subui** | Interactive Shiny dashboard | No (install separately) |

## Exported Functions

| Function | Purpose |
|---|---|
| `core_packages()` | List the 6 auto-attached package names |
| `r4sub_packages()` | Show all packages with installed version and attachment status |
| `r4sub_status()` | Check which ecosystem packages are installed |
| `r4sub_conflicts()` | Report function name conflicts with other loaded packages |
| `r4sub_news()` | Show NEWS entries for each ecosystem package |
| `r4sub_cite()` | Print citation information for regulatory or academic use |

## Managing Conflicts

If another loaded package exports a function with the same name as an R4SUB function, use the `::` operator to be explicit:

```r
r4subcore::validate_evidence(ev)
r4subscore::compute_sci(pillar_scores)
```

Run `r4sub_conflicts()` after `library(r4sub)` to see any collisions.

## License

MIT
