What this is
A draft RFC (Request for Comments) proposing the minimum set of fields that a research group would need to share with the community safety pool to provide an anonymized adverse-event record. Pooled safety data is core to the open-source thesis; it's what compresses the regulatory timeline from decades to years. A workable schema is the prerequisite that hasn't been built yet.
Why this matters
Without a schema, every research group that wants to share safety data invents its own format, and pooling becomes impossible. With a schema, even a v0.1 pooling becomes mechanical. This is genuinely strategic work; the person who does it will have shaped how the whole community shares safety data going forward.
What to do
- Comment to claim.
- Read the linked context (regulatory references, existing standards like CDISC / OHDSI).
- Draft an RFC with these sections:
- Motivation: why a community safety-data schema is needed
- Goals and non-goals: what this schema is and isn't
- Proposed schema: structured field-by-field spec
- Anonymization rules: the floor for HIPAA / GDPR alignment
- Open questions: things you want community input on
- References: standards consulted
- Open the RFC as a PR with the title
RFC: Safety-data schema v0.1.
- Comment on this issue when the RFC PR is open so the lane lead can attach reviewers.
Definition of done
Skills
- Research methodology
- Basic data modeling
- IRB / HIPAA / regulatory awareness
- Comfortable writing structured technical proposals
Scope estimate
8–12 hours.
Helpful starting points
How to claim this issue
- Comment "I'd like to work on this." We'll assign it to you.
- Open a draft RFC PR within ~3 weeks of being assigned.
- Ask any scoping questions on this issue or in our Discord
#contributing channel.
Contact: community@openwater.health
By contributing, you agree to our Contributor License Agreement. (If the CLA isn't yet live when you start, we'll handle it once the flow is up.)
What this is
A draft RFC (Request for Comments) proposing the minimum set of fields that a research group would need to share with the community safety pool to provide an anonymized adverse-event record. Pooled safety data is core to the open-source thesis; it's what compresses the regulatory timeline from decades to years. A workable schema is the prerequisite that hasn't been built yet.
Why this matters
Without a schema, every research group that wants to share safety data invents its own format, and pooling becomes impossible. With a schema, even a v0.1 pooling becomes mechanical. This is genuinely strategic work; the person who does it will have shaped how the whole community shares safety data going forward.
What to do
RFC: Safety-data schema v0.1.Definition of done
Skills
Scope estimate
8–12 hours.
Helpful starting points
How to claim this issue
#contributingchannel.Contact: community@openwater.health
By contributing, you agree to our Contributor License Agreement. (If the CLA isn't yet live when you start, we'll handle it once the flow is up.)