Recipe template

Save a copy as docs/src/content/docs/recipes/<ehr>-<what-it-gets>.md, for example epic-hba1c-lab-results.md.

---
title: Getting <data> from <EHR>
description: One sentence on what this recipe gets and for which measure.
ehr: epic            # epic | oracle-health | athenahealth | eclinicalworks | modmed | nextech | nextgen |
                     # practice-fusion | greenway | compulink | eyemd | elation | veradigm | other
measures: [CMS122]   # one or more measure ids
fhirVersion: R4      # DSTU2 | STU3 | R4 | R5
contributor: Your Name
organization: Your Organisation   # optional
lastVerified: 2026-10-01          # date you last confirmed this works
sandbox: true                     # true if tested in the vendor's public sandbox
---

## Goal

What data you are getting, and which measure it is for.

## Prerequisites

App registration, scopes, settings the health system must enable, and the inputs you need
(for example, the patient list).

## Steps

1. Which FHIR resource to request, with which search parameters.
2. What to keep and what to discard.
3. Which fields to read.

## Gotchas

The EHR-specific surprises. This is the most valuable section — be specific.

## How to verify

How to tell you got complete, correct data.

## References

Links to the FHIR specification, the measure specification and vendor documentation.

Fields title, description, ehr, measures, contributor and lastVerified are required; the pull request check fails without them.