Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can bring health-data exports into one local analytics workspace with DuckDB and dbt: keep untouched source files, query them with DuckDB, and use dbt to build repeatable, documented tables. This is for personal exploration—not a medical record system, clinical decision tool, or guarantee of privacy.
What DuckDB and dbt each do
DuckDB is an embedded analytical database: it runs within your local workflow rather than requiring you to operate a separate database server. The dbt-duckdb adapter lets dbt run transformations against DuckDB and persist modeled relations in a DuckDB file. The adapter documents working with CSV, JSON, and Parquet inputs, including querying files directly. See the dbt-duckdb adapter documentation and DuckDB guides.
dbt adds structure around transformations: models can be documented and tested, and dbt invocations produce machine-readable artifacts useful for project metadata and documentation. These tools help make an analysis reproducible; neither establishes that a transformation is medically meaningful. Artifact names and behavior vary by dbt version. See dbt artifacts documentation.
Choose a local workflow or a managed service
| Consideration | Local DuckDB + dbt CLI | Managed FHIR or analytics service |
|---|---|---|
| Where data lives | On your computer and in any locations where you keep backups or synced copies; you manage those locations. | In a cloud service, subject to its configuration, account controls, and export destinations. |
| Setup and upkeep | Requires a technically comfortable user to install tools, manage files, and maintain backups and access controls. | Requires cloud-account setup, permissions, and service configuration; it brings a cloud operating model rather than removing operational work. |
| Interoperability | Works with file exports such as CSV, JSON, and Parquet. Clinical exports depend on what your provider makes available. | A FHIR service can provide FHIR-oriented storage and export features, but access and scope depend on configuration and authorization. |
| Costs | No price is established here; consider your computer, storage, and backup arrangements. | No price is established here; cloud usage and related services may have costs. |
| Likely fit | A personal, exploratory workflow where you want local file control and accept self-management. | An adjacent option for organizations or projects needing a managed FHIR environment, not an assumed fit for an individual. |
dbt’s supported-platform page lists DuckDB as generally available for “DuckDB (CLI only)” and says this status applies to dbt v2.0 and later; it also warns that local adapter lifecycle can differ from the dbt platform lifecycle. The adapter README retrieved for this workflow describes support targets of dbt-core 1.8.x or later and DuckDB 1.0.0 or later. These are separate compatibility statements, not a promise that every combination works; check current requirements before installing. See dbt supported data platforms and the adapter README.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Set the boundary before importing health data
Treat this project as a personal analysis workspace, not your authoritative chart. Do not use its output to diagnose, change treatment, or replace advice from a qualified clinician. Keep your provider’s record and instructions as the clinical source of truth.
Local storage is not inherently secure, and running dbt locally does not make a project “HIPAA compliant.” In the United States, HHS explains that HIPAA generally does not protect health information accessed through or stored on personal phones and tablets; data downloaded or entered into most personal-use apps may also fall outside HIPAA unless the app is provided by a covered entity or business associate. HHS notes that other entities may access data, including for advertising or data-broker activity. The rules differ by jurisdiction, and other laws may apply. Read HHS guidance on HIPAA and health information on personal devices.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
Inventory exports and keep originals unchanged
Start with the export options you can actually obtain. Record the source, available formats, date range, time zone or timestamp conventions, units, and how to request a fresh export. Save original exports without editing them; build cleaned tables separately so you can revisit assumptions or reprocess the source.
A simple folder convention is an author-recommended pattern, not a requirement of DuckDB or dbt:
Rank #3
- Capacity Display Variance: 500GB external ssd often appears as around 465GB on Windows. MacOS can show full 500 GB capacity. This is binary calculation difference and doesn’t affect SSD hard drive actual physical storage
- 1050 MB/s Speed: Instantly access to your files with blazing-fast 10Gbps external SSD read up to 1050MB/s and write up to 1000MB/s. LED Light indicates USB SSD instant activity
- Data Security: Solid state drives S.M.A.R.T. health diagnostics and adaptive TRIM optimizing data block management ensures consistent write speeds and extends the longevity of the portable SSD
- USB-C & USB-A Cable: Both cables featuring rapid USB 3.2 Gen2, this USB SSD effortlessly bridges devices, enabling seamless cross-platform file transfers and backup between computers, smartphones, tablets and iPhone
- Always Fast: No slowdowns for large file transfers. With SLC caching (25% of current available capacity allocated as high-speed cache), this external SSD delivers steady 10Gbps for transfers within the cache capacity
health-project/
data/
raw/
provider-a/
wearable-b/
dbt_project/
analytics.duckdbInclude a source and export date in directory or file names when practical. Keep a small project note describing what each export contains, its units and time zone, known missing periods, and when it was refreshed. DuckDB’s guides cover loading and querying common file formats; the adapter README describes external CSV, JSON, and Parquet inputs.
Build a traceable model sequence
- Connect dbt to a DuckDB file. Configure the dbt-duckdb adapter and its profile path so modeled relations persist in a local DuckDB database. Follow the adapter’s current installation and configuration instructions rather than assuming that version targets remain unchanged.
- Stage each source with its original meaning intact. Create source-specific staging models that expose fields clearly and avoid silently changing units or interpreting ambiguous codes. Keep original files as the recoverable input layer.
- Normalize only what you can explain. In intermediate models, document timestamp conversions, unit conversions, identifier handling, and any deduplication. Preserve source-specific fields where a mapping is uncertain instead of pretending that unlike measures are equivalent.
- Make focused analysis models. Build a model for a defined question—such as summarizing measurements by day—rather than creating a broad “health score” whose assumptions are difficult to audit.
- Document refresh and transformation assumptions. Note when each source was exported, how a refresh replaces or appends data, what time zone is used, and what missingness remains. Keep a record of model changes and dbt run outputs.
Test data shape, not clinical truth
Use dbt tests for properties you have reason to expect. Tests can reveal that assumptions stopped holding; a passing test does not validate a diagnosis, measurement, or clinical conclusion.
Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
- Check uniqueness only for keys that the source or your model actually defines as unique.
- Check required timestamps where the source is expected to provide them, and retain or report records that fail rather than quietly discarding them.
- Restrict units to known values only when the source’s unit conventions are documented.
- Use expected row ranges only when you know the source’s coverage and refresh behavior; missing days can be real gaps, not a problem to fill automatically.
- Show nulls and missing periods explicitly. Do not invent values to make a chart look continuous.
dbt artifacts can support documentation, state, source-freshness display, test-coverage calculations, timing analysis, and review of historical project changes. What is generated depends on your dbt version and invocation; consult the artifact reference.
Recommended Free Tools
Use FHIR bulk export only when your source supports it
FHIR bulk export is an optional route to clinical records, not a universal export feature. It requires a server that supports the capability and authorization for the requested data. The HL7 Bulk Data Access guide describes authenticated requests and asynchronous retrieval; servers should return only resources the client is authorized to access, and the export scope depends on server implementation and permissions. See the current HL7 FHIR Bulk Data Access Implementation Guide.
Best Value
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
A typical bulk workflow involves requesting an export, waiting for the server’s response or completion status, then retrieving the files it provides. The exact endpoint, authorization flow, supported filters, and file availability are server-specific. Follow the provider’s instructions and respect individual sharing preferences; do not assume that a FHIR endpoint exists just because a provider uses FHIR internally.
AWS HealthLake is one specific managed-service example, not a general personal-health recommendation. Its documentation describes exporting NDJSON files to S3, with one resource type per object, and details service-specific IAM and SMART-related requirements. See AWS HealthLake export documentation. That setup entails cloud accounts, permissions, and storage configuration rather than a purely local workflow.
Protect copies, backups, and credentials
Your security depends on the computer, accounts, backup locations, and sync services involved—not just on the database file. Reduce exposure by keeping only the copies you need and controlling access to every place data is stored.
- Use your operating system’s account protections and available device encryption; choose settings appropriate to your device and threat model.
- Protect cloud and provider credentials, and review who can access synced folders and backups.
- Do not put raw exports, database files, credentials, or screenshots containing health details in a public repository.
- Understand how long each copy is retained and how to remove it from local storage, synced folders, and backups.
- Keep a backup that you can restore, and periodically verify that the backup process still works.
These are practical precautions, not a claim that any particular configuration meets a legal or regulatory standard.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
