Skip to content

Add compliance-config.json#1405

Open
allaway wants to merge 1 commit into
Sage-Bionetworks:developfrom
allaway:compliance-config
Open

Add compliance-config.json#1405
allaway wants to merge 1 commit into
Sage-Bionetworks:developfrom
allaway:compliance-config

Conversation

@allaway

@allaway allaway commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds compliance-config.json at the repo root to satisfy the ARPA-H BDF ENHANCE Scorecard compliance-configuration check. The file is the regulatory-applicability questionnaire (HIPAA / FDA / EHI / children's-data boolean flags), using the canonical 18-key format also used by other BDF program tools (e.g. helxplatform/Koios, alico-cra/bdf-mock-tool).

Profile chosen

synapseclient is characterized as low-risk, data-agnostic research data-management infrastructure — a client library/CLI that transfers whatever files a user provides, with PHI/governance handled at the Synapse platform level rather than inherent to the client. Accordingly, every flag is false except is_low_risk: true.

Flag Value
collects_health_info false
has_identifiable_health_info false
is_health_plan false
is_healthcare_provider false
offers_certified_hit false
enables_ehi_exchange false
requires_prescription false
works_for_covered_entity false
intended_for_medical_use false
is_administrative_or_lifestyle_only false
is_low_risk true
has_fda_regulated_function false
is_consumer_facing false
interacts_with_phr false
intended_for_children false
has_child_oriented_features false
children_using_app false
offers_substance_use_treatment false

Validation

  • Parses as valid JSON (18 keys).
  • Repo pre-commit hooks (check-json, etc.) pass.

⚠️ For maintainers

These are compliance attestations, not dummy values. Please have the Sage program lead / compliance confirm the regulatory posture before treating this as authoritative — in particular collects_health_info, has_identifiable_health_info, works_for_covered_entity, and is_consumer_facing were judgment calls (both example BDF tools set is_consumer_facing: true; this PR sets it false since the client is a developer/researcher tool).

🤖 Generated with Claude Code

Adds the ARPA-H BDF ENHANCE Scorecard regulatory-applicability
questionnaire (compliance-config.json) at the repo root. Uses the
canonical 18-key format used by other BDF program tools. synapseclient
is characterized as low-risk, data-agnostic research infrastructure:
all flags false except is_low_risk.

These are compliance attestations that should be signed off by the
Sage program lead / compliance before being treated as authoritative.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@allaway allaway requested a review from a team as a code owner June 11, 2026 16:11
Comment thread compliance-config.json
"is_administrative_or_lifestyle_only": false,
"is_low_risk": true,
"has_fda_regulated_function": false,
"is_consumer_facing": false,

@andrewelamb andrewelamb Jun 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the caveat that I don't know what these fields mean exactly: Is this correct? I would argue that the PythonClient IS consumer facing.

Comment thread compliance-config.json
"is_low_risk": true,
"has_fda_regulated_function": false,
"is_consumer_facing": false,
"interacts_with_phr": false,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also argue the PythonClient DOES interact with PHR

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PHR? personal health record?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants