Diabetes indication routed out of the policy

**My Thought Process on Medical Policy MP-331: GLP-1 Receptor Agonists for Chronic Weight Management**

Right, let's break down this specific case concerning Medical Policy MP-331, which deals with GLP-1 Receptor Agonists for chronic weight management. The policy's effective date is January 1, 2026, and its scope is very specific: it *only* governs the weight-management indication. This is a crucial point. The policy explicitly states that requests related to type 2 diabetes are handled under the pharmacy benefit and are therefore outside the purview of this particular policy. They are to be routed as "N/A" (not applicable).

Now, let's look at the member information provided. We have a 57-year-old member, and the requested drug is Semaglutide. The stated indication for this request is "Glycaemic control in type 2 diabetes mellitus." Furthermore, the prescriber has provided a clear statement: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control." This statement directly reinforces that the primary intent is for diabetes management. The clinical data shows a BMI of 30.1 and an HbA1c of 8.4%, which, while indicating obesity and uncontrolled diabetes, further supports the prescriber's assertion about the diabetes indication.

Given the explicit wording in the policy – "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)" – and the prescriber's clear statement that this is *not* a weight-loss request, but rather for "glycaemic control in type 2 diabetes mellitus," the situation becomes straightforward.

Therefore, my decision is "not_applicable". According to the instructions for "not_applicable" scenarios, the criteria array should be empty. The rationale needs to clearly explain *why* it's not applicable. The core reason is that the request falls outside the defined scope of MP-331. The policy specifically directs that requests for type 2 diabetes management, such as this one for glycaemic control, are handled by the pharmacy benefit and are to be routed as N/A, rather than being evaluated under this weight management policy.

I've double-checked the policy wording about routing as "N/A" and the instruction for "not_applicable" to return an empty criteria array. This seems to align perfectly. The member's HbA1c of 8.4% further solidifies the diabetes indication. My final rationale is: "The request is for glycaemic control in type 2 diabetes. Per the policy scope, these requests are governed by the pharmacy benefit and are not applicable to MP-331." This is concise and accurately reflects the policy's intent and the case specifics.

**My Thought Process on Navigating Medical Policy MP-331 for a GLP-1 Receptor Agonist Request**

Right, so I've been presented with a request for Semaglutide for a 57-year-old member. My primary task here is to determine if this request falls under Medical Policy MP-331, which specifically covers GLP-1 Receptor Agonists for Chronic Weight Management, and is slated to become effective on January 1, 2026.

The crucial detail is the stated indication. The request explicitly states it's for "glycaemic control in type 2 diabetes mellitus." This is reinforced by the prescriber's statement: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control." The clinical details provided – an HbA1c of 8.4% and a BMI of 30.1 – further confirm the focus on diabetes management.

Now, looking at MP-331, its scope is explicitly defined as "weight-management indication only." The policy also provides a specific instruction: "Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." This is the linchpin of my decision-making process here.

Because the request is squarely for type 2 diabetes glycaemic control and *not* for weight management, it falls outside the purview of MP-331. The policy's direct instruction is to route such requests as "not_applicable" (N/A). This means I shouldn't be approving or denying it under MP-331; it simply isn't the policy that governs this specific use case. The pharmacy benefit is where this request should be directed.

Therefore, my decision must be "not_applicable." Consequently, the `criteria` array should be empty, as per the instructions for N/A determinations.

For the `rationale`, I need to articulate this concisely, staying under 40 words and in one or two sentences, while clearly explaining why this request is being routed as N/A. I need to ensure it reflects the policy's intent.

Initially, I considered: "The request is for type 2 diabetes glycaemic control, not weight management. Per policy instructions, requests for type 2 diabetes are outside the scope of MP-331 and should be routed as N/A." (36 words). This is good.

However, refining it to be even more direct about the policy's exclusion: "The request is for type 2 diabetes glycaemic control, which is explicitly excluded from MP-331 and must be routed as not applicable." (22 words). This is quite clear and concise.

Let me re-evaluate the nuance. The policy states it *governs* weight management and that diabetes requests are *outside* it. So, my rationale should reflect that exclusion.

My latest consideration for the rationale is: "The request is for type 2 diabetes glycaemic control, which is outside the scope of MP-331. The policy specifies that such requests should be routed as not applicable." (32 words). This clearly states the reason for exclusion from the policy and the resulting action. It fits the word count and the need for clarity.

So, to summarize my final output for this request:
*   **Decision:** "not_applicable"
*   **Criteria:** `[]` (an empty array)
*   **Rationale:** "The request is for type 2 diabetes glycaemic control, which is outside the scope of MP-331. The policy specifies that such requests should be routed as not applicable."

I've double-checked the JSON keys and values, the logic for N/A, the word count, and the clarity of the rationale. Everything aligns perfectly with the policy instructions and the specific details of this member's request.

My thought process for evaluating this prior authorization request for semaglutide, against medical policy MP-331, was quite straightforward once I delved into the specifics.

First, I meticulously analyzed the request itself. I noted the member's age (57), the requested medication (semaglutide), and crucially, the stated indication. The prescriber was very clear: "glycaemic control in type 2 diabetes mellitus," and explicitly stated, "not a weight-loss request." This initial piece of information was the most critical clue. I then reviewed the clinical data provided. The HbA1c of 8.4 percent unequivocally confirms the presence of type 2 diabetes. I also noted the BMI of 30.1 (calculated from the provided height and weight), and the fact that the member had completed diabetes self-management education. I checked for any mention of step therapy for weight-loss agents, which was absent, and confirmed there were no contraindications like medullary thyroid carcinoma, MEN2, or pregnancy.

Next, I turned my attention to the medical policy, MP-331. I immediately observed its title: "GLP-1 RECEPTOR AGONISTS FOR CHRONIC WEIGHT MANAGEMENT." This title strongly suggested the policy's focus. I then read the scope section very carefully, and it confirmed my suspicion. It explicitly states, "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." The subsequent approval and reauthorization criteria (A, B, C, R1, R2), as well as the exclusions and documentation sections, all pertained to *chronic weight management*.

This led me to the direct comparison between the request and the policy. The core of the discrepancy was this: the request was for type 2 diabetes, while the policy was exclusively for weight management. The policy's scope section provided a definitive instruction on how to handle such situations: route them as "not_applicable" because they are outside the policy's purview.

Therefore, the decision became clear: "not_applicable." There was no basis for approving or denying this request under MP-331 because the policy simply did not cover the stated indication.

Following the established guidelines for a "not_applicable" decision, I understood that the `criteria` array should be empty.

For the rationale, I needed to succinctly explain *why* the policy didn't apply. I formulated it to be direct and accurate, emphasizing the core mismatch: "The request is for type 2 diabetes. This policy governs only GLP-1 agonists for chronic weight management and is not applicable to requests for diabetes management." This statement is under 40 words and precisely captures the reasoning.

Finally, I assembled the JSON output with the `decision` set to "not_applicable," an empty `criteria` array, and the formulated `rationale`. This systematic approach, starting with understanding the request and then meticulously cross-referencing it with the policy's explicit scope and instructions, ensured the correct and justifiable outcome.

Alright, let's break down this prior authorization request for semaglutide. As a health plan analyst, my primary job here is to meticulously apply Medical Policy MP-331 to the information provided.

First and foremost, I need to have a crystal-clear understanding of what MP-331 actually covers. My internal notes tell me this policy is strictly for the **chronic weight management indication** of GLP-1 receptor agonists. Crucially, it explicitly **excludes** requests for type 2 diabetes. Those are handled under the pharmacy benefit, and for the purpose of *this* policy, they should be marked as "not_applicable."

The policy outlines specific criteria for both initial approvals and reauthorizations. For an initial approval, I'm looking for a certain BMI range (>=30, or 27-29.9 with a comorbidity), evidence of a lifestyle intervention (diet and exercise for at least three months), and a trial of step-therapy agents like phentermine-topiramate or naltrexone-bupropion for eight weeks (or a documented contraindication/intolerance). For reauthorization, the patient needs to have demonstrated at least a 5% weight loss and continued lifestyle intervention. There are also explicit exclusions, such as a history of thyroid or endocrine issues, pregnancy, or plan benefit exclusions. And of course, there are documentation pends if key information like BMI or step-therapy dates are missing.

Now, let's turn to the specific request I have in front of me. I'm looking at a 57-year-old member requesting semaglutide. The prescriber's notes are very clear here: they state the indication is "for glycaemic control in type 2 diabetes mellitus" and emphatically add, "This is not a weight-loss request." This is immediately a red flag for the applicability of MP-331. The provided HbA1c of 8.4 percent further confirms the type 2 diabetes diagnosis.

Even though I see a BMI of 30.1, which *could* meet a weight-management criterion, and I note the lifestyle information provided (diabetes education, not a specific reduced-calorie diet and increased physical activity for 3 months) and the lack of step-therapy trial for weight-loss agents, these details become secondary. My core focus is on the stated indication.

The very first sentence of MP-331 is the decisive factor here. It states, "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

Since the request is unequivocally for the treatment of type 2 diabetes, MP-331 is simply not the correct policy to apply. Therefore, my decision on this request, under MP-331, must be "not_applicable." I won't be evaluating the clinical criteria for weight management because the request falls outside the scope of this specific policy.

So, to summarize my thought process in terms of the output:

*   **Decision:** The policy explicitly directs me to route type 2 diabetes requests as "not_applicable," so that's what I'll select.
*   **Criteria:** For a "not_applicable" decision under this policy, the instructions specify returning an empty array for the `criteria` field.
*   **Rationale:** My rationale needs to be concise and directly address why the policy doesn't apply. I'll state that the request is for type 2 diabetes, and that MP-331 is solely for chronic weight management, therefore not applicable here. This aligns perfectly with the policy's own wording.

Essentially, I've done a quick read of the request, identified the stated indication, and immediately cross-referenced it with the very first and most critical exclusionary clause of the policy I'm supposed to be applying. The rest of the clinical details are interesting but ultimately irrelevant to my decision under MP-331 itself.

Here's my thought process in analyzing this prior authorization request.

First and foremost, I need to identify the core task: I'm acting as a health plan analyst tasked with reviewing a prior authorization request for a GLP-1 receptor agonist. My output needs to be a JSON object detailing my decision, the criteria I applied, and the rationale behind my decision, all strictly in accordance with the provided medical policy, MP-331.

My immediate priority is to thoroughly understand MP-331. I'll break it down:

1.  **Policy Title:** "GLP-1 RECEPTOR AGONISTS FOR CHRONIC WEIGHT MANAGEMENT." The title itself is a significant clue about its scope.
2.  **Effective Date:** 2026-01-01. The request is dated 2026, so this policy is current and applicable.
3.  **Scope:** This is the *crucial* section. It explicitly states: "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." This sentence is the linchpin. It tells me precisely how to handle requests for diabetes versus weight management.
4.  **Approval Criteria (A, B, C):** These are for weight management.
    *   A: BMI thresholds (>=30 or 27-29.9 with comorbidities).
    *   B: A documented lifestyle intervention (diet/exercise for at least 3 months).
    *   C: A required step therapy trial of specific agents (phentermine-topiramate or naltrexone-bupropion).
5.  **Reauthorization Criteria (R1, R2):** Not relevant for an initial request.
6.  **Exclusions (X1, X2, X3):** These are conditions that would lead to denial *if the policy applied*. They include history of thyroid/endocrine issues, pregnancy, or plan benefit exclusions.
7.  **Documentation for Pend (E1, E2):** These are reasons for requesting more information, like missing BMI or step therapy dates.

Now, I turn my attention to the specifics of the authorization request itself:

*   **Member Information:** A 57-year-old.
*   **Requested Drug:** Semaglutide, which is indeed a GLP-1 receptor agonist.
*   **Indication:** This is where I pay extremely close attention. The prescriber has *explicitly stated* the request is for "glycaemic control in type 2 diabetes mellitus." They even went further to clarify, "This is not a weight-loss request." This is a direct contradiction to the policy's stated scope.
*   **Clinical Details:**
    *   HbA1c: 8.4 percent. This confirms the presence of type 2 diabetes.
    *   Current Medications: Metformin monotherapy, typical for type 2 diabetes.
    *   Height/Weight: 171 cm, 88.0 kg, yielding a BMI of 30.1. This *would* meet criterion A1 for weight management.
    *   Lifestyle Intervention: "diabetes self-management education completed 2026-02". This is a documented intervention, but it's unclear if it meets the "at least 3 months" requirement of criterion B for weight management.
    *   Step Therapy: No trial of phentermine-topiramate or naltrexone-bupropion is documented. This would likely fail criterion C for weight management.
    *   Exclusions: No apparent thyroid/endocrine history, and not pregnant.

The moment of synthesis arrives. I'm comparing the request's stated purpose against the policy's defined scope.

The policy, MP-331, is *unambiguously* for "CHRONIC WEIGHT MANAGEMENT." The request, however, is for "glycaemic control in type 2 diabetes mellitus," with a clear disclaimer from the prescriber that it's "not a weight-loss request."

The policy's scope section provides explicit instructions for this exact scenario: "Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

Therefore, the critical insight is that MP-331 simply *does not apply* to this request. I don't need to evaluate criteria A, B, C, R, X, or E because the fundamental prerequisite for applying the policy – that it be for weight management – is not met. The correct action is to mark it as "not_applicable."

Finally, I construct the JSON output according to the specifications:

*   **decision:** Based on the policy's scope and the prescriber's stated indication, this must be `"not_applicable"`.
*   **criteria:** The instructions dictate that for a "not_applicable" decision, the `criteria` field should be an empty array, so `[]`.
*   **rationale:** This needs to concisely explain *why* the policy is not applicable. It should highlight the policy's scope and the request's indication. My rationale is: "This policy is for chronic weight management. The requested indication is type 2 diabetes, which is outside the scope of this policy and governed by the pharmacy benefit." This is concise and directly addresses the governing principle.

This entire process, from dissecting the policy to carefully examining the request and then matching them against the explicit instructions, leads me to the definitive "not_applicable" decision and the accompanying JSON structure.

The task is to evaluate a prior authorization request based on Medical Policy MP-331.
The policy MP-331 governs "GLP-1 RECEPTOR AGONISTS FOR CHRONIC WEIGHT MANAGEMENT".
It explicitly states: "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

The authorization request states:
"Requested drug: semaglutide, indicated by the prescriber for glycaemic control in type 2 diabetes mellitus. The prescriber's letter states explicitly: 'This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control.'"

Since the request is for type 2 diabetes and explicitly not for weight loss, it falls outside MP-331.
Therefore, the decision should be "not_applicable".
The criteria array should be empty [].
The rationale should explain that the request is for type 2 diabetes, which is outside the scope of MP-331 and governed by the pharmacy benefit.

Decision: not_applicable
Criteria: []
Rationale: The request is for type 2 diabetes glycaemic control, not weight management, and is therefore outside the scope of this policy.

Let's double check the rules:
"not_applicable"   the policy does not govern this request at all
For "not_applicable", return an empty array.

Rationale: under 40 words.
"The request is for type 2 diabetes glycaemic control, not weight management, and is therefore outside the scope of this policy." -> 20 words.

JSON format:
```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The request is for type 2 diabetes glycaemic control, not weight management, and is therefore outside the scope of this policy."
}
```
All good.

Let me analyze this task carefully.

The request is for semaglutide, but the prescriber explicitly states it's for glycaemic control in type 2 diabetes mellitus, not for weight management. The policy MP-331 governs the weight-management indication ONLY. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy — route as N/A rather than approving or denying under MP-331.

The prescriber's letter explicitly says: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control."

So the policy does not govern this request. Decision: "not_applicable". Criteria: empty array.

Rationale: The policy governs weight management only; this request is for T2DM glycaemic control, which is routed to the pharmacy benefit. So it should be N/A under MP-331.

The required keys:
- "decision": "not_applicable"
- "criteria": [] (empty array)
- "rationale": one or two sentences under 40 words.

Even though the member has BMI 30.1 (which would satisfy A1), the request is for diabetes, not weight management. The policy explicitly says route as N/A.

Rationale: "The request is for glycaemic control in type 2 diabetes, not weight management; MP-331 governs weight management only and directs diabetes requests to the pharmacy benefit as N/A." That's about 30 words.

Let me count: "The request is for glycaemic control in type 2 diabetes, not weight management; MP-331 governs weight management only and directs diabetes requests to the pharmacy benefit as N/A." — 28 words. Good.

JSON output:
```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The prescriber explicitly requests semaglutide for type 2 diabetes glycaemic control, not weight management. MP-331 governs weight management only, so this request is routed to the pharmacy benefit as not applicable."
}
```

Word count: "The prescriber explicitly requests semaglutide for type 2 diabetes glycaemic control, not weight management. MP-331 governs weight management only, so this request is routed to the pharmacy benefit as not applicable." = 30 words. Under 40. Good.

Let me analyze this task carefully.

The policy MP-331 governs GLP-1 receptor agonists for chronic weight management only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331).

The request is for semaglutide, explicitly indicated by the prescriber for glycaemic control in type 2 diabetes mellitus. The prescriber explicitly states "This is not a weight-loss request."

So this is a type 2 diabetes request, which is outside MP-331. The correct decision is "not_applicable" with an empty criteria array.

Even though the member has a BMI of 30.1 (which would satisfy A1), and other details, the indication is glycaemic control in T2DM, not weight management. The policy explicitly says requests for type 2 diabetes are outside this policy — route as N/A.

X3 (weight-loss drug exclusion) — we don't have info that the member's plan carries a weight-loss drug exclusion, and more importantly, this isn't a weight-management request anyway. The policy says to route T2DM requests as N/A rather than approving or denying under MP-331. So X3 doesn't apply here since this isn't a weight-management request.

Decision: not_applicable
Criteria: empty array []
Rationale: The request is for glycaemic control in type 2 diabetes, which is governed by the pharmacy benefit, not MP-331. Route as N/A.

Let me write the rationale in one or two sentences under 40 words:

"The prescriber explicitly requests semaglutide for type 2 diabetes glycaemic control, not weight management. Per MP-331, diabetes requests fall under the pharmacy benefit and are routed as not applicable rather than evaluated under this policy."

That's about 40 words. Let me count: "The prescriber explicitly requests semaglutide for type 2 diabetes glycaemic control, not weight management. Per MP-331, diabetes requests fall under the pharmacy benefit and are routed as not applicable." — that's 30 words. Good.

Actually let me trim a bit more: "The prescriber explicitly states this is a type 2 diabetes glycaemic control request, not weight management. MP-331 governs weight management only; diabetes requests route to the pharmacy benefit as not applicable." — about 32 words. Fine.

JSON output:
```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The prescriber explicitly states this is a type 2 diabetes glycaemic control request, not weight management. MP-331 governs weight management only, so this routes to the pharmacy benefit as not applicable."
}
```

Rationale word count: The(1) prescriber(2) explicitly(3) states(4) this(5) is(6) a(7) type(8) 2(9) diabetes(10) glycaemic(11) control(12) request(13) not(14) weight(15) management(16). MP-331(17) governs(18) weight(19) management(20) only(21) so(22) this(23) routes(24) to(25) the(26) pharmacy(27) benefit(28) as(29) not(30) applicable(31). — 31 words, under 40. Good.

We need answer JSON only. Need apply policy MP-331. The policy governs weight-management indication only. Requests for type 2 diabetes are governed by pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331). The request drug semaglutide indicated by prescriber for glycemic control in type 2 diabetes. Prescriber letter states not weight-loss request, T2DM HbA1c 8.4 on metformin, adding GLP-1 for glycemic control. So policy does not govern this request at all. Decision: "not_applicable". Criteria: empty array (per instructions: For "not_applicable", return an empty array). Rationale: one or two sentences under 40 words. Need explain that indication is type 2 diabetes/glycemic control, policy governs weight-management only; route to pharmacy benefit / N/A. Ensure no extra keys. Money not relevant.

Need be careful: The task says "not_applicable" when policy does not govern this request at all. Yes. Criteria empty array. Rationale string under 40 words.

Let's craft rationale: "The request is for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so it does not apply; route under the pharmacy benefit." Count words: The(1) request(2) is(3) for(4) glycaemic(5) control(6) in(7) type(8) 2(9) diabetes(10), not(11) chronic(12) weight(13) management(14). MP-331(15) governs(16) only(17) the(18) weight-management(19) indication(20), so(21) it(22) does(23) not(24) apply(25); route(26) under(27) the(28) pharmacy(29) benefit(30). Under 40. Good.

Need include exactly one fenced JSON code block. Use json with keys decision, criteria, rationale. decision "not_applicable". criteria [].

Double-check if any nuance: Policy says "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." The request says semaglutide indicated for glycemic control in T2DM. So not_applicable. Criteria empty array. Good.

Check if criteria should include something like "X" or "N/A"? Instructions: For "not_applicable", return an empty array. Good.

Rationale: under 40 words, one or two sentences. Good.

Potential issue: The requested drug semaglutide could be Wegovy vs Ozempic? But policy explicitly says weight-management indication only, requests for T2DM governed by pharmacy benefit outside. Prescriber states not weight-loss. So N/A. Exclusions (X1-X3) are under policy and only apply if policy governs? Since not applicable, no need evaluate. The plan weight-loss exclusion X3? Not provided, but no matter. Step therapy no trial, BMI 30.1, lifestyle etc irrelevant. Decision N/A.

Need output exactly fenced block, nothing else. Ensure valid JSON. No trailing commas. Use null? Not needed.

Let's produce final.

We need answer prior auth per MP-331. The request is semaglutide indicated for glycemic control in T2DM, with explicit statement not weight-loss request, HbA1c 8.4. Policy MP-331 governs weight-management indication only. Requests for type 2 diabetes are governed by pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331). So decision = not_applicable. criteria = empty array. rationale: one or two sentences under 40 words. Need explain policy covers only chronic weight management; request is T2DM glycemic control, outside policy, route N/A. Must be under 40 words. Let's count: "MP-331 governs only chronic weight management. This request is for glycaemic control in type 2 diabetes, so it is outside the policy and routed as not applicable." Word count: MP-331(1) governs(2) only(3) chronic(4) weight(5) management(6). This(7) request(8) is(9) for(10) glycaemic(11) control(12) in(13) type(14) 2(15) diabetes(16), so(17) it(18) is(19) outside(20) the(21) policy(22) and(23) routed(24) as(25) not(26) applicable(27). Under 40. Good.

Need output exactly one fenced JSON code block. Required keys: decision, criteria, rationale. decision "not_applicable". criteria [].

Double-check: The policy says requests for type 2 diabetes are governed by pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331). It also says This policy governs the weight-management indication only. Indicated by prescriber for glycaemic control in T2DM. So N/A. criteria empty array. Rationale string. Ensure no other keys. Use JSON null if needed? No. Not needed.

Need be careful with spelling: "glycaemic" vs "glycemic". The prompt uses "glycaemic control" in request. Policy says "type 2 diabetes". Rationale can use "glycaemic" or "glycemic"? Either fine. Use "glycaemic" to match. But JSON string safe. Use plain ASCII? JSON allows Unicode. We'll use "glycaemic".

Let's craft final.

Potential nuance: Height/weight and BMI 30.1, lifestyle DSME, step therapy none, no exclusions. But since T2DM indication, we do not apply A/B/C. Even though BMI 30.1 and lifestyle DSME? Actually lifestyle intervention documented? Diabetes self-management education completed 2026-02, not necessarily reduced-calorie diet and increased physical activity for at least 3 months. Step therapy no trial. It would deny maybe due to step? But N/A supersedes. The policy says route as N/A rather than approving or denying under MP-331. So decision not_applicable. Good.

Check criteria: For not_applicable, return empty array. Yes.

Rationale under 40 words: "MP-331 governs only chronic weight management. The request is for glycaemic control in type 2 diabetes, which is a pharmacy-benefit indication outside this policy, so it is not applicable." Count: MP-331(1) governs(2) only(3) chronic(4) weight(5) management(6). The(7) request(8) is(9) for(10) glycaemic(11) control(12) in(13) type(14) 2(15) diabetes(16), which(17) is(18) a(19) pharmacy-benefit(20) indication(21) outside(22) this(23) policy(24), so(25) it(26) is(27) not(28) applicable(29). 29 words. Good.

Need ensure "pharmacy-benefit" hyphenated counts maybe as one word? Doesn't matter under 40.

One more nuance: The policy says route as N/A rather than approving or denying under MP-331. The output decision values include "not_applicable" exactly. Yes.

Let's produce fenced JSON block exactly. No other text.

We need answer task. Need parse policy and request. Need output JSON only with decision, criteria array, rationale string.

Let's analyze.

Medical Policy MP-331 — GLP-1 receptor agonists for chronic weight management. Effective 2026-01-01. "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

Authorization request: Member 57-year-old. Requested drug: semaglutide, indicated by prescriber for glycaemic control in type 2 diabetes mellitus. Prescriber letter explicitly: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control."
Height/weight 2026-03-08: 171 cm, 88.0 kg. BMI 30.1.
Lab HbA1c 8.4.
Lifestyle: diabetes self-management education completed 2026-02.
Step therapy: no trial of phentermine-topiramate or naltrexone-bupropion.
Thyroid/endocrine history: none. Not pregnant.

We need apply policy as written. Decision options: approve, deny, pend, not_applicable. Since request for T2DM glycaemic control, not weight management. Policy governs weight-management indication only. It says requests for type 2 diabetes are governed by pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331). So decision should be "not_applicable". Criteria empty array. Rationale under 40 words: one or two sentences. It should explain that MP-331 governs weight-management only; request is for type 2 diabetes glycaemic control, so outside policy; route as N/A. Need maybe mention no criteria evaluated? The policy says route as N/A rather than approving/denying. Criteria empty array per output contract: For "not_applicable", return an empty array.

Let's check nuance. The requested drug is semaglutide. The policy is GLP-1 receptor agonists for chronic weight management. It governs weight-management indication only. Request states for glycaemic control in T2DM. Even though member meets BMI 30.1? But indication is not weight loss. It says route as N/A rather than approving or denying under MP-331. So decision = not_applicable. Criteria = [].

Need rationale string: one or two sentences, under 40 words. Example: "The request is for semaglutide for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A." Count words: The(1) request(2) is(3) for(4) semaglutide(5) for(6) glycaemic(7) control(8) in(9) type(10) 2(11) diabetes(12), not(13) chronic(14) weight(15) management(16). MP-331(17) governs(18) only(19) the(20) weight-management(21) indication(22), so(23) the(24) request(25) is(26) outside(27) this(28) policy(29) and(30) is(31) routed(32) as(33) N/A(34). 34 words. Good.

Need ensure no extra keys. JSON:
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The request is for semaglutide for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A."
}

Check if criteria empty array. Yes.

Wait: The task says: "Choosing the criteria: For 'not_applicable', return an empty array." Good.

Check: decision string exactly one of "approve", "deny", "pend", "not_applicable". "not_applicable" has underscore. Yes.

Need output exactly one fenced JSON code block and nothing else. Ensure no text outside. Use code block with json. Include newline? It says exactly one fenced JSON code block. I'll output:

```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The request is for semaglutide for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A."
}
```

Double-check if any nuance about "semaglutide" maybe there are forms: semaglutide for weight management (Wegovy) vs for T2DM (Ozempic). Requested drug semaglutide indicated for glycaemic control. Policy governs weight-management indication only. It says requests for type 2 diabetes are governed by pharmacy benefit and outside policy. So yes N/A.

Could there be a potential trap: Diagnosis is type 2 diabetes, but the policy is for GLP-1 receptor agonists for chronic weight management. The request supplies BMI 30.1 and other lifestyle/step therapy etc. But indication is explicitly not weight loss. The policy says: route as N/A rather than approving or denying under MP-331. So decision not_applicable. Criteria empty. Rationale one or two sentences under 40 words. The rationale I wrote is two sentences. Word count 34. Good. Ensure no currency or dates needed.

Let's consider if there's any instruction about "where a plan document, medical policy, or measure specification is supplied, that document governs, even where it differs from real-world rule." The policy says outside policy route as N/A rather than approving/denying. So not_applicable correct.

Check the output contract: "Reply with exactly one fenced JSON code block and nothing else. No preamble, no commentary before or after, no second code block." Good.

One more thought: The policy header says "MEDICAL POLICY MP-331 — GLP-1 RECEPTOR AGONISTS FOR CHRONIC WEIGHT MANAGEMENT ... This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." Wait: It says "route as N/A rather than approving or denying under MP-331". In the output contract, decision "not_applicable": the policy does not govern this request at all. That exactly matches.

Need maybe criteria: [] because not applicable. Rationale: Should I mention "prescriber explicitly states not a weight-loss request"? Yes to show why not weight management. My rationale: "The request is for semaglutide for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A." It doesn't mention prescriber explicit, but okay. Maybe include "prescriber states" to be clear? Let's see word count: "The prescriber states the request is for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A." Count: The(1) prescriber(2) states(3) the(4) request(5) is(6) for(7) glycaemic(8) control(9) in(10) type(11) 2(12) diabetes(13), not(14) chronic(15) weight(16) management(17). MP-331(18) governs(19) only(20) the(21) weight-management(22) indication(23), so(24) the(25) request(26) is(27) outside(28) this(29) policy(30) and(31) is(32) routed(33) as(34) N/A(35). Still under 40. Good.

Maybe "type 2 diabetes" with no "mellitus" okay. Or include "T2DM"? Not needed. Use "type 2 diabetes". Rationale should be plain.

Let's finalize. Ensure JSON valid: rationale string has no unescaped quotes. Good. criteria empty array. decision string. No extra keys.

Final answer:

```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The prescriber states the request is for glycaemic control in type 2 diabetes, not chronic weight management. MP-331 governs only the weight-management indication, so the request is outside this policy and is routed as N/A."
}
```
Wait: I need verify no second code block. Just one fenced block. Good.

 We need to parse the medical policy MP-331 and the authorization request.

Policy MP-331 governs GLP-1 receptor agonists for chronic weight management. It explicitly states: "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

The request: semaglutide indicated for glycaemic control in type 2 diabetes mellitus. Prescriber explicitly says: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control."

Therefore, the request is for type 2 diabetes, not weight management. The policy says route as N/A (not_applicable) rather than approving or denying under MP-331.

So decision: "not_applicable".

Criteria: empty array.

Rationale: Must be one or two sentences, under 40 words. Something like: "The request is for glycaemic control in type 2 diabetes, which is outside the scope of MP-331 and governed by the pharmacy benefit." Let's count words. "The request is for glycaemic control in type 2 diabetes, which is outside the scope of MP-331 and governed by the pharmacy benefit." That's 20 words. Good.

Check constraints: exactly one fenced JSON code block and nothing else.

Keys: decision, criteria, rationale.

decision: "not_applicable"
criteria: []
rationale: "The request is for glycaemic control in type 2 diabetes, which is outside the scope of MP-331 and governed by the pharmacy benefit."

Wait, need to ensure no extra whitespace or commentary. Let's produce JSON.

Double-check: Are there any other nuances? The policy says: "Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)." So yes, not_applicable.

The request includes height and weight, BMI, etc. But because it's not a weight management request, we don't evaluate those.

Thus answer is straightforward.

Make sure to format JSON exactly. 

 The user wants me to apply the medical policy MP-331 to a prior authorization request and return a JSON with specific keys: decision, criteria, rationale.

Let me analyze the policy and the request:

Policy MP-331: GLP-1 Receptor Agonists for Chronic Weight Management
Effective 2026-01-01. This policy governs the weight-management indication only.
Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331).

The request:
- Member: 57-year-old
- Requested drug: semaglutide
- Indication: glycaemic control in type 2 diabetes mellitus
- Prescriber explicitly states: "This is not a weight-loss request. The member has type 2 diabetes with an HbA1c of 8.4 percent on metformin monotherapy and I am adding a GLP-1 for glycaemic control."

Policy explicitly says: "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

So this is a request for type 2 diabetes, not weight management. According to the policy, this should be "not_applicable" because the policy does not govern this request at all.

Now let's check the output requirements:
- decision: "not_applicable"
- criteria: empty array (for not_applicable)
- rationale: one or two sentences, under 40 words

I need to make sure the rationale is concise and explains why.

Criteria: empty array [].

Rationale options:
- "The policy governs weight-management indication only; type 2 diabetes requests are outside its scope."
- "Request is for glycemic control in type 2 diabetes, not weight management, so MP-331 does not apply."

Word count check:
"The request is for type 2 diabetes glycemic control, which is outside the scope of MP-331." = 15 words. Good.

Wait, let me double-check if there's any trick. The member has BMI 30.1, but the prescriber explicitly says it's for diabetes. The policy says route as N/A rather than approving or denying. So decision is definitely "not_applicable".

Keys required: "decision", "criteria", "rationale".

JSON format only. No extra text.

Let me construct:

```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "The request is for glycemic control in type 2 diabetes, which is outside the scope of MP-331."
}
```

Word count: 15 words. Good.

Wait, should I mention it's governed by pharmacy benefit? The policy says "Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy". So I can mention that.

Alternative:
"MP-331 governs weight management only; type 2 diabetes requests are handled under the pharmacy benefit."

11 words. Good.

I think either is fine. Let me make sure it's clear.

Decision: not_applicable
Criteria: []
Rationale: MP-331 governs weight management only; type 2 diabetes requests are outside its scope.

Actually the policy says "route as N/A rather than approving or denying under MP-331". So not_applicable is correct.

I will output exactly the JSON block.

Let me carefully analyze this authorization request against medical policy MP-331.

**Key facts from the request:**
- Member: 57-year-old
- Requested drug: semaglutide
- Indication: glycaemic control in type 2 diabetes mellitus (explicitly NOT weight-loss)
- Prescriber explicitly states: "This is not a weight-loss request"
- BMI: 30.1 (meets A1)
- HbA1c: 8.4% (indicates type 2 diabetes)
- Height/weight: 171 cm, 88.0 kg (2026-03-08)
- Lifestyle: diabetes self-management education completed 2026-02
- Step therapy: NO trial of phentermine-topiramate or naltrexone-bupropion
- No thyroid/endocrine contraindications, not pregnant

**Policy analysis:**

The critical piece here is the very first sentence of the policy:
"This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

The prescriber has explicitly stated this is NOT a weight-loss request. It is a request for glycaemic control in type 2 diabetes. The indication is diabetes management, not weight management.

Therefore, this request is **NOT APPLICABLE** to MP-331. The policy explicitly states to "route as N/A rather than approving or denying under MP-331" for type 2 diabetes requests.

The decision should be: "not_applicable"
The criteria array should be: [] (empty, as the policy does not govern this request)
The rationale should explain that this is a diabetes indication, not a weight-management indication.

Let me verify this interpretation:
- The policy is titled "GLP-1 RECEPTOR AGONISTS FOR CHRONIC WEIGHT MANAGEMENT"
- Effective 2026-01-01, and the current date of 2026-09-01 falls within the active window
- The request is explicitly for diabetes glycaemic control, not weight management, which the opening paragraph excludes from scope
- Diabetes-indicated requests route through the pharmacy benefit instead

This confirms the case is unambiguous — decision "not_applicable," empty criteria array, with rationale noting the request targets type 2 diabetes glycaemic control rather than chronic weight management, placing it outside MP-331's scope.

Let me carefully analyze this authorization request against MP-331.

First, let me identify what's being requested:
- The request is for semaglutide, indicated for glycaemic control in type 2 diabetes mellitus
- The prescriber explicitly states this is NOT a weight-loss request
- The member has type 2 diabetes with HbA1c of 8.4% on metformin monotherapy

Now let me look at the policy's scope:
MP-331 states: "This policy governs the weight-management indication only. Requests for type 2 diabetes are governed by the pharmacy benefit and are outside this policy (route as N/A rather than approving or denying under MP-331)."

This is a critical statement. The request is explicitly for type 2 diabetes management, not weight management. The prescriber has explicitly stated this is for glycaemic control, not weight loss.

Therefore, this request is OUTSIDE the scope of MP-331. According to the policy instructions, I should route this as "not_applicable" because the policy does not govern this request at all.

Let me double-check:
- Is this a weight-management indication? No - it's explicitly for glycaemic control in type 2 diabetes
- Does MP-331 govern requests for type 2 diabetes? No - the policy says these are governed by the pharmacy benefit and are outside this policy
- Should I route as N/A? Yes - explicitly instructed to do so

Decision: "not_applicable"
Criteria: [] (empty array, as instructed for not_applicable)
Rationale: The request is for glycaemic control in type 2 diabetes, explicitly stated as not a weight-loss indication. MP-331 governs only the weight-management indication; type 2 diabetes requests are outside this policy.

Let me format this properly:

```json
{
  "decision": "not_applicable",
  "criteria": [],
  "rationale": "Requested indication is type 2 diabetes glycaemic control, explicitly not weight management. MP-331 governs weight-management only; diabetes requests are outside this policy."
}
```

That rationale is concise and clear, well under any length constraints. This accurately captures the reasoning - the policy simply doesn't apply here since it's scoped to weight management only, and this is a diabetes glycaemic control request.