Connect patient health records

Install this skill

npx skills add StanfordSpezi/SpeziVibe --skill fasten-ehr-integration

Or install all skills: npx skills add StanfordSpezi/SpeziVibe --skill '*'. See the Getting Started guide for tool-specific options.

Explore this skill in browser chat. Each button opens a new conversation; bring any earlier briefs with you and save the results yourself.

Try in ClaudeTry in ChatGPT

Need to paste the prompt yourself?

Browser prompt for fasten-ehr-integration

Please act as the SpeziVibe `fasten-ehr-integration` skill and walk me through it interactively.

STEP 1 — Fetch the skill instructions from this URL and read them carefully:
https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/fasten-ehr-integration/SKILL.md

If the skill references other files or other skills by name, fetch them from the same repository:
- Files inside this skill (e.g. `references/foo.md`): https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/fasten-ehr-integration/<relative-path>
- Other skills (e.g. `biodesign-needs-finding`): https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/<skill-name>/SKILL.md

STEP 3 — Walk me through the skill interactively. When a step would normally save a markdown file to a project, show the file content in a code block instead so I can copy it. Don't simulate my answers — wait for me to respond.

If you cannot fetch the skill instructions or their reference files, ask me to paste them before proceeding.
Ask me to paste or attach any existing briefs you need. Do not claim to have read files, run commands, created a project, or tested an integration from this chat. Help me prepare the decisions and instructions, then hand off file and code work to my coding tool.

If your chat can’t open the skill link, open the instructions in a new tab and paste them into the chat.

Browser chat can help with architecture and planning decisions. Building and testing the integration requires a coding tool, a project, and a Fasten developer account. If the app does not exist yet, save the planning decisions first and schedule the working integration in the implementation plan.

Walks you through connecting your app to real EHR data with Fasten Connect: patients link their own patient portals through an embedded widget, your backend requests a bulk FHIR export, and a webhook delivers the records into your app's own storage. The skill verifies each stage as you build — keys, widget, export, webhook, parsing — and finishes with a mandatory data-privacy walkthrough covering exactly where the health data travels and what obligations come with holding it.

What It Produces

• A working, sandbox-tested Fasten Connect integration (widget → export → webhook → local records)
• A data-flow and privacy decision walkthrough (HIPAA right-of-access framing, FTC HBNR, business-associate and research/IRB branches — not legal advice)
• docs/planning/ehr-connection-brief.md recording the architecture and privacy decisions for downstream skills

Output

Produces docs/planning/ehr-connection-brief.md alongside the integration code.

Example

AI:   What's your backend stack, and can it receive public HTTPS
      requests — or are we developing locally?

You:  Next.js, running locally for now.

AI:   Then we'll use a tunnel for webhook delivery during development.
      First: create your developer account at
      portal.connect.fastenhealth.com and grab the test-mode keys —
      I'll set up the env config and a key smoke test while you do.
      ...
AI:   Export downloaded: 325 FHIR resources for the Epic sandbox
      patient. Before we go further — here is exactly where that
      data traveled, and the decisions you now own as its custodian.