Skip to content

Healthcare Bundle

This example shows how SCS bundle structure maps to a healthcare application that needs to incorporate HIPAA compliance requirements alongside internal architectural standards.

This is an advanced example — most teams start with the solo developer or team setup guides.

bundle:prior-auth-app:DRAFT # Project bundle (AI entry point)
↓ imports
bundle:acme-health-corp:1.0.0 # Domain bundle (company aggregator)
↓ imports
bundle:acme-architecture:1.0.0 # Concern bundle (architecture standards)
bundle:acme-security:1.0.0 # Concern bundle (security standards)
bundle:acme-clinical:1.0.0 # Concern bundle (clinical workflows)
↓ imports
bundle:hipaa:1.0.0 # Standards bundle (HIPAA requirements)
↓ imports
bundle:meta:1.0.0 # Meta bundle (SCS foundation)

When Claude Code loads the project bundle, it recursively resolves all imports and loads the combined SCD content from every bundle in the hierarchy.

id: bundle:prior-auth-app
type: project
version: "DRAFT"
title: Prior Authorization Application
description: AI context for the prior auth workflow application
scds:
- scd:project:prior-auth-domain
- scd:project:prior-auth-api-patterns
imports:
- bundle:acme-health-corp:1.0.0
provenance:
created_by: Engineering Lead
created_at: 2025-01-15T10:00:00Z
rationale: Project-specific context for prior auth development

When a developer opens Claude Code on this project, Claude loads:

  • HIPAA compliance requirements
  • Acme’s internal security standards
  • Clinical workflow constraints
  • Project-specific API patterns and conventions

All from structured, versioned files that the team reviews and maintains together.