SovereignHealthLedger

A cryptographic framework for digital health credential management built upon the Nostr messaging overlay.

System Premise

SovereignHealthLedger furnishes an immutable, user-governed repository for sensitive clinical artifacts leveraging the Nostr overlay network. This architecture empowers individuals with absolute dominion over their biometric and diagnostic telemetry, while permitting audited, permissioned disclosure to authorized clinical entities.

Core Capabilities

• Immutable storage of clinical documents leveraging Nostr event structures
• Fine-grained, cryptographic access policy enforcement
• Identity verification mechanism for participating medical practitioners
• Universal accessibility across browser and portable device interfaces
• Pervasive, end-to-end cryptographic protection for all payload data

Technology Stack

• Client-Side: React framework, TypeScript language, TailwindCSS utility framework
• Server-Side Logic: Node.js runtime environment
• Data Persistence: SQLite relational engine integrated via Drizzle ORM
• Interoperability Protocol: Nostr Protocol Specification

Initiation Guide

Pre-requisites

• Node.js (version 18 or subsequent release)
• Package manager: npm or yarn

Setup Procedure

1. Repository acquisition bash git clone https://github.com/HealthNoteLabs/Npub.Health.git cd Npub.Health

2. Dependency resolution bash npm install

3. Environmental Configuration bash cp .env.example .env # Modify the newly created .env file with requisite configuration values

4. Launching the development environment bash npm run dev

Project Hierarchy

Npub.Health/ ├── client/ # Presentation layer (React application) ├── server/ # Application logic (Node.js services) ├── shared/ # Common utilities and type definitions ├── scripts/ # Auxiliary operational scripts └── ...

Development Lifecycle

Executing in Development Mode

bash npm run dev

Production Artifact Generation

bash npm run build

Collaboration Guidelines

We welcome external contributions! Please initiate the process by submitting a comprehensive Pull Request.

Licensing Declaration

This software is distributed under the terms of the MIT License; consult the LICENSE file for specifics.

Communication Channels

Direct inquiries or feature suggestions should be formalized as an issue within this repository.

AWS Infrastructure Provisioning for Auxiliary Blossom Brokerage

This project incorporates modules designed for the automated deployment of Blossom Broker instances onto Amazon Web Services EC2 virtual machines, enabling users to self-provision dedicated compute resources.

Deployment Workflow

1. Dependency Installation (AWS SDK):

npm install @aws-sdk/client-ec2

1. Security Group Initialization: The script located at scripts/create_aws_security_groups.js is responsible for provisioning requisite firewall rules across specified AWS regions: bash node scripts/create_aws_security_groups.js

Ensure the placeholder VPC identifier within the script is accurately populated for each target region.

1. Credential Configuration: Populate the .env file with necessary AWS access parameters:

AWS_ACCESS_KEY_ID=your_access_key_id AWS_SECRET_ACCESS_KEY=your_secret_access_key

# Pre-provisioned Security Group Identifiers per region (output from prior script) SECURITY_GROUP_US_EAST=sg-xxxxxxxxxxxxxxxx SECURITY_GROUP_US_WEST=sg-xxxxxxxxxxxxxxxx SECURITY_GROUP_EU_CENTRAL=sg-xxxxxxxxxxxxxxxx SECURITY_GROUP_AP_SOUTHEAST=sg-xxxxxxxxxxxxxxxx

# Persistent Data Store Connection String DATABASE_URL=postgres://postgres:postgres@localhost:5432/npubhealth

1. Database Schema Finalization: PostgreSQL installation and database creation (npubhealth) are required. Execute schema migrations via: bash npm run db:push

2. Verification Test Run: bash npm run dev

Operational Architecture Components

1. EC2 Orchestrator (server/aws/ec2Manager.ts): Manages the lifecycle (creation, status polling) of compute instances.
2. Broker Health Agent (server/aws/serverMonitor.ts): A recurring process for status telemetry collection.
3. Management Interface (server/routes.ts): Exposes HTTP endpoints for infrastructure control.
4. State Repository (server/db): Handles the persistent storage for broker metadata and operational states.

Standardized User Provisioning Trajectory

1. User selects configuration profile (instance size, geographical region, unique name).
2. System generates a preliminary monetary remittance identifier.
3. Payment transaction is executed (simulated during non-production testing).
4. Provisioning script initiates an EC2 launch, embedding the Blossom broker bootstrapping sequence.
5. User Interface continuously queries the instance status until the 'Operational' state is confirmed.
6. Connectivity is established to the user's dedicated Blossom endpoint.

Security Protocols

• Security group ingress rules permit traffic on standard web ports (80, 443) and the application service port (3000).
• SSH port access must be constrained to whitelisted IP addresses in live deployments.
• AWS credentials must adhere strictly to the Principle of Least Privilege (PoLP).
• Production deployments should favor IAM roles over embedded access keys.

Debugging Guidelines

If operational anomalies arise:

1. Validate AWS authentication material and IAM policy adherence.
2. Confirm security group rules are correctly applied.
3. Review server-side deployment logs for initialization failures.
4. Inspect the database state for anomalous record entries.

Consult the Official AWS SDK Documentation for SDK utility reference.

Note on Cloud Computing Definition (ISO Context): Cloud infrastructure represents an evolution beyond traditional data center operational models, prioritizing virtualization and standardized access interfaces.