> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/changelog/2025/prescription-level-icds-automations-expansion-and-waf-hardening.md).

# Prescription-Level ICDs, Automations Expansion & WAF Hardening

*Released September 16, 2025*

**Web Application Firewall Throttling Updates**: adjustments to WAF throttling limits, as part of ongoing API security hardening.

**ICD codes on a prescription level**: each prescription on an encounter now carries its own list of ICDs, phasing out encounter-level ICDs. No partner action is required — ICD codes sent via deprecated encounter-level endpoints/fields are automatically applied to all of the encounter's prescriptions; the same applies to auto-added obesity ICDs based on patient BMI.

**Automations expansion**: new triggers and steps — Create Vouchers, Send Emails and Messages, Call HTTP endpoints, context-based wildcards, and more.

## \[Clinicians App]

* ICD codes now attached to prescriptions instead of encounters; removed ICD filter from the encounters list
* Fixed "fix button" showing for incorrect state
* New flag identifying encounters originated from CarePair
* Requirement for a note when rejecting encounters
* Improvements to Cases List visibility
* New translation options for Medical Intake (question titles now translated too)

## \[Patient App]

* Support for requirement logic based on date of birth under 1 year
* Support for wildcards in hardcoded question content

## \[Web Platform]

* Added CarePair and ICD fields to the offerings list
* New experience for associating CarePair offerings
* Toggle to hide the "new virtual visit" screen
* New automation triggers and steps
* Improved wildcard presentation on fields, new pickers
* New program field on offerings to categorize prescriptions/encounters
* New pricing tiers capabilities

## \[API]

* New auditing platform


---

# 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.mdintegrations.com/changelog/2025/prescription-level-icds-automations-expansion-and-waf-hardening.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.