Compliance GL5197E (Wegovy)
Validation Checks by Instafill.ai
1
Required Plan Member Coverage Identifiers Present (Contract/Certificate/Sponsor)
Validates that Plan Contract Number, Plan Member Certificate Number, and Plan Sponsor are all provided and not left blank. These identifiers are required to locate the correct benefits plan and route the request to the right sponsor/coverage. If any are missing, the submission should be rejected or pended with a request for the missing identifiers because adjudication cannot proceed reliably.
2
Plan Member and Patient Name Completeness and Character Validation
Checks that first and last names for both plan member and patient are present, and that name fields contain only expected characters (letters, spaces, hyphens, apostrophes) and do not contain numbers or symbols. This reduces mismatches in member/patient identification and prevents downstream system errors. If validation fails, the form should be returned for correction and the record should not be created/updated.
3
Date of Birth Format and Validity (dd/mmm/yyyy) for Plan Member and Patient
Ensures Plan Member Date of Birth and Patient Date of Birth follow the required format (dd/mmm/yyyy, e.g., 05/JAN/2010) and represent real calendar dates. Correct DOB formatting is critical for eligibility checks, dependent validation, and clinical criteria (pediatric vs adult). If invalid or missing, the submission should be flagged as incomplete and held until corrected.
4
Age Consistency with Selected Diagnosis Path (Pediatric vs Adult)
Validates that the patient’s age derived from Patient Date of Birth is logically consistent with the diagnosis section selected (pediatric vs adult criteria). This prevents applying the wrong clinical rules and avoids inappropriate approvals/denials. If inconsistent (e.g., adult age with pediatric criteria), the submission should be pended for clarification or corrected diagnosis selection.
5
Canadian Address Validation for Plan Member (Province and Postal Code)
Checks that Province is selected/entered as a valid Canadian province/territory and that Postal Code matches Canadian format (A1A 1A1) and is consistent with the province when possible. Accurate address data is required for mail notifications and jurisdictional handling (e.g., Quebec routing). If invalid, the form should be rejected or pended because notifications and processing may fail.
6
Patient Preferred Daytime Phone Number Format Validation
Validates that the preferred daytime phone number is present and matches an acceptable phone format (e.g., 10-digit NANP with optional country code, parentheses, spaces, or hyphens). Contact information is required to resolve clinical/administrative questions quickly and avoid delays. If invalid or missing, the submission should be pended and the requester asked to provide a reachable number.
7
Email Address Format Validation (Optional Field)
If an email address is provided, verifies it conforms to standard email syntax (local@domain) and does not contain spaces or invalid characters. This supports secure site notifications and reduces failed communications. If invalid, the system should either reject the email value (while allowing submission) or pend if email is required for a chosen communication workflow.
8
Mutually Exclusive Yes/No Checkbox Enforcement (All Binary Questions)
Ensures that for each Yes/No question (e.g., other group plan coverage, transferred benefits, provincial application/approval, PAP enrollment, GLP-1 combination, dose exceeds 2.4 mg), exactly one option is selected. Selecting both or neither creates ambiguity and can lead to incorrect adjudication logic. If the rule is violated, the submission should be flagged as invalid and returned for correction.
9
Other Group Plan Conditional Requirements and Attachments
If 'Other group plan drug coverage' is Yes, validates that the other insurer name, other plan contract number, other certificate number, and whether the drug is covered under the other plan are completed. If the drug is not covered under the other plan, the decline reason must be provided and a decline notice attachment should be present; if previously covered, proof of payment/EOB should be attached. If any conditional fields/attachments are missing, the request should be pended because coordination of benefits and eligibility for Manulife consideration cannot be confirmed.
10
Provincial Program Application/Decision Logic and Required Reasons
Validates that if provincial application is marked No, a reason is provided; and if provincial approval is marked No, a decline reason is provided. This is important because the plan may require provincial coverage to be pursued first and needs documentation to assess supplemental coverage. If missing, the submission should be pended until the reason (and any required provincial decision documentation, where applicable) is supplied.
11
Patient Assistance Program (PAP) Enrollment Conditional Details
If PAP enrollment is Yes, checks that case manager first/last name, phone, email, program name, and program ID are provided and properly formatted (phone/email rules applied). These details enable coordination and verification of support programs that may affect coverage and cost-sharing. If incomplete, the submission should be pended because follow-up and coordination may be delayed.
12
Treatment Administration Location Selection and Facility Details When Not Home
Validates that exactly one treatment administration location is selected (Home, MD office, Private Clinic, Hospital In-Patient, Hospital Out-patient). If the location is not Home, requires clinic/hospital name, telephone, and full address (street, city, province, postal code) to be completed; if MD office is in a hospital, requires the description field. If these are missing, the submission should be pended because site-of-care impacts assessment, billing, and coordination.
13
Drug Strength and Dosage Completeness and Dose Limit Consistency
Checks that Drug Strength and Dosage is populated with a meaningful regimen (strength and frequency at minimum) and is consistent with the 'Will dose of Wegovy exceed 2.4mg once weekly?' response. This prevents unclear prescriptions and ensures the request aligns with plan criteria and product labeling constraints used in prior authorization rules. If missing or contradictory (e.g., dosage indicates >2.4 mg weekly but checkbox says No), the submission should be pended for physician clarification.
14
Diagnosis Selection Required and Single-Path Completion
Validates that at least one diagnosis pathway is selected (pediatric initial/renewal, adult initial/renewal, MI risk reduction initial/renewal, or Any Other Diagnosis) and that the form is not completed across conflicting pathways simultaneously. Each pathway drives different clinical criteria and required fields, so mixing them can cause incorrect decisions. If no pathway is selected or multiple incompatible pathways are selected, the submission should be rejected/pended for correction.
15
Baseline Measurements Numeric Validation (Weight and BMI) and Plausibility
Ensures baseline body weight and BMI fields (where required by the selected pathway) are numeric, include reasonable decimal precision, and fall within plausible human ranges (with configurable thresholds). Accurate measurements are essential for eligibility (e.g., BMI thresholds, percent weight loss) and clinical appropriateness. If non-numeric, missing, or implausible, the submission should be pended and the prescriber asked to correct the values.
16
Adult Initial Comorbidity Dependency and 'Other' Specification
If 'weight-related comorbid condition present' is Yes, validates that at least one comorbidity checkbox is selected; if 'Other' is selected, the free-text other condition must be provided. This ensures the clinical rationale for therapy is documented and supports consistent adjudication. If comorbidity details are missing, the submission should be pended because eligibility criteria may not be met or cannot be verified.
17
Drug History Table Date Format/Order and Outcome Completeness
Validates that each entered prior/current therapy row has a drug name, start date and end date in yyyy/mmm format, and that end date is not earlier than start date (or is blank only if clearly indicated as ongoing per business rules). Also checks that at least one outcome (Intolerance or Inadequate/Suboptimal Response) is selected for each completed row, and that the 'continuing medication' Yes/No is answered. If incomplete or inconsistent, the submission should be pended because step-therapy/previous trial requirements cannot be assessed.
18
No Previous Therapies Rationale Required When Drug History Is Empty
If no drug therapy entries are provided in the drug history section, validates that at least one rationale checkbox (risk of interaction/contraindication/other) is selected and that the medical rationale narrative is completed. This prevents missing clinical justification when prior therapies have not been attempted. If absent, the submission should be rejected or pended because the prior authorization criteria often depend on documented prior therapy attempts or valid exceptions.
19
Physician Identity, License, and Contact Information Completeness
Ensures prescribing physician first/last name, college/license number, specialty, address, and telephone/fax are provided and formatted appropriately (phone/fax numeric formats; license number non-empty and pattern-checked if jurisdiction rules exist). This is required for verification, follow-up, and auditability of the medical attestation. If missing, the submission should be pended because the request cannot be validated as prescriber-authorized.
20
Signature and Signature Date Presence and Chronology (Physician and Plan Member)
Validates that both Physician Signature and Plan Member Signature are present, and that their corresponding dates are provided in dd/mmm/yyyy format and are not in the future. Optionally checks chronology (e.g., physician signature date should not be after plan member signature date by an unreasonable margin, or vice versa per business policy). If signatures/dates are missing or invalid, the submission must be rejected because consent and medical certification are legally required for processing.