> For the complete documentation index, see [llms.txt](https://docs.healthsherpa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.healthsherpa.com/on-exchange-api-documentation/integration-guide/use-cases-and-features/operationalizing-healthsherpa-exports.md).

# Operationalizing HealthSherpa Exports

If you're not already using our exports today, see [here](https://faq.healthsherpa.com/en/articles/5211027-exporting-client-lead-data) to learn about this powerful agency management tool.&#x20;

{% hint style="info" %}
Dig deeper into the export data fields and their sources [here](https://app.box.com/s/x8glk2tuaydxtvzq1ymk6rlb5znl0pdv).
{% endhint %}

## FAQ and Errors

* I don't see all of my enrollments in the file. What applications are included?&#x20;
  * Applications that were submitted via a three-way call to the Marketplace are not included in the export, since they were submitted off-platform.&#x20;
* What does it mean when `healthsherpa_policy_ids` is null?&#x20;
  * The policies were cancelled or terminated.&#x20;
* Who is agent of record on a given policy?&#x20;
  * The `aor_npn`  field is what CMS shows as the agent of record as of the last EDE sync. EDE syncs only happen when 1) a user manually accesses a record (agent clicks a client name, consumer logs in), 2) an agent clicks "Refresh" for a record, or 3) HealthSherpa does a quarterly "bulk sync" with CMS, where we get current status for every app on our platform. The value for `aor_npn` is a snapshot as of the last sync, and may be stale.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.healthsherpa.com/on-exchange-api-documentation/integration-guide/use-cases-and-features/operationalizing-healthsherpa-exports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
