common

The common skill serves as the foundational infrastructure layer for the entire HealthSim ecosystem, enabling seamless data flow and integration between specialized product modules like PatientSim, MemberSim, RxMemberSim, and TrialSim. It is designed for developers, data engineers, and researchers who need to maintain state across complex simulation sessions, link disparate healthcare entities into a unified person record, or perform high-performance analytical queries on synthetic datasets.

At its core, this skill provides persistent storage management, allowing users to snapshot, save, and restore entire patient or member cohorts. By utilizing SSN as a universal correlator, the framework ensures that a person tracked in the clinical domain is correctly mapped to their corresponding payer claims, pharmacy records, and clinical trial participation data. It also exposes a direct interface to the underlying DuckDB database, providing the capability to execute complex SQL queries, inspect schema structures, and pull reference data directly from the local workspace storage.

• State Management: Robust persistence operations supporting cohort save, load, resume, and snapshot functionality to facilitate iterative scenario building.

• Identity Correlation: Advanced cross-product linking using Social Security Numbers (SSN) as the master key to correlate patient clinical records, member claims, and trial subject identifiers.

• DuckDB Integration: Direct SQL database access for schema exploration, ad-hoc data analysis, and advanced cohort filtering across simulated populations.

• Data Flow Coordination: Enables the cohesive movement of data between PatientSim, MemberSim, and TrialSim to build end-to-end healthcare journeys.

• Use this skill when you need to persist large-scale synthetic data or audit outcomes across multiple clinical episodes.

• Ideal for verifying data consistency between different modules, such as ensuring a patient's clinical diagnosis aligns with their generated medical claims.

• Supports batch operations and automated persistence, which is critical for high-volume scenario generation and token-efficient simulation testing.

• Practical constraints: Ensure all generated identifiers follow the established HealthSim schema definitions to maintain successful cross-reference linkage.

• Use SQL commands for debugging unexpected output or for extracting specific demographic metrics from the integrated DuckDB instance.