Compliance GL5197E (Ozempic)
Validation Checks by Instafill.ai
1
Ensures Plan Contract Number and Certificate Number are present and in an acceptable identifier format
Validate that both the Plan contract number and Plan member certificate number are provided, since they are required to locate eligibility and benefits. Enforce a reasonable identifier pattern (e.g., alphanumeric, length bounds, no unsupported symbols) and trim leading/trailing spaces. If either value is missing or fails format rules, the submission should be rejected or routed to manual review because the request cannot be reliably matched to a plan/member record.
2
Validates plan member and patient names for completeness and character rules
Check that required name fields (first and last) are populated for both plan member and patient, and that middle initial is either blank or a single letter. Names should not contain digits or disallowed punctuation, and should meet minimum length requirements to reduce data-entry errors. If validation fails, prompt correction because inaccurate names can prevent matching to plan records and can delay authorization decisions.
3
Validates date fields use required formats and represent real calendar dates
Validate that plan member DOB, patient DOB, physician signature date, and plan member signature date match the form’s required formats (dd/mmm/yyyy for DOB/signature dates; yyyy/mmm for drug history start/end dates). Ensure the dates are valid (e.g., no 31/Feb) and month abbreviations are recognized consistently (e.g., Jan, Feb, Mar). If invalid, block submission because incorrect dates can break eligibility checks, renewal timing, and audit trails.
4
Checks age and date logic for plan member/patient and signature dates
Ensure DOBs are not in the future and that the plan member/patient ages are within plausible bounds (e.g., 0–120 years). Verify signature dates are not in the future and are not unreasonably earlier than the form completion context (e.g., far in the past), and that physician signature date is present when physician section is completed. If these checks fail, flag for correction or manual review because they indicate likely data entry errors or invalid attestations.
5
Validates Canadian address fields and province/postal code consistency
Require plan member mailing address fields (street, city, province, postal code) and validate postal code format as Canadian (e.g., A1A 1A1) with optional space. Confirm the province is a valid Canadian province/territory and that the postal code’s first letter is consistent with the selected province where feasible. If invalid or incomplete, reject or request correction because mailing decisions and jurisdictional rules (e.g., Quebec handling) depend on accurate address data.
6
Validates phone number formats for patient and provider contacts
Validate patient preferred daytime phone number and any clinic/hospital/physician phone/fax numbers using a consistent rule set (e.g., 10-digit NANP with optional country code, allowing separators, and optional extension only in the extension field). Ensure the extension field contains only digits and is not embedded in the main phone number field. If validation fails, require correction because missing/invalid contact numbers can prevent clinical follow-up and delay authorization.
7
Validates email address format when provided (patient and case manager)
If patient email or case manager email is provided, validate it against standard email syntax (single @, valid domain, no spaces) and normalize casing/whitespace. Email is optional for the patient, but if present it must be usable for notifications; case manager email is required when the Patient Assistance Program is marked Yes. If invalid, prompt correction because unusable emails undermine notification workflows and case coordination.
8
Enforces mutually exclusive Yes/No selections for all binary questions
For each Yes/No pair (e.g., other group plan coverage, recent transfer to Manulife, provincial application made, provincial approval, patient assistance enrollment, and all clinical Yes/No items), ensure exactly one option is selected. Prevent both boxes being checked or neither being checked when the question is required by the chosen pathway. If this fails, block submission because ambiguous answers prevent correct adjudication and downstream conditional requirements.
9
Validates conditional completion for Other Group Plan section when coverage is Yes
If 'Other Group Plan Coverage' is Yes, require the other insurer name, other plan contract number, other certificate number, and whether the drug is covered under that plan (Yes/No). If the drug is not covered, require an explanation and the presence of an attached decline notice indicator; if covered, require proof-of-payment/benefits documentation indicator. If conditional fields are missing, route back for completion because coordination of benefits and eligibility for Manulife consideration depends on these details.
10
Validates conditional completion for Recent Coverage Change questions
If the plan sponsor recently transferred drug benefits to Manulife is Yes, require an answer to whether the member previously received coverage for this drug through the prior insurer. If that prior coverage is Yes, require an attachment indicator for proof of payment/EOB as stated on the form. If missing, flag for follow-up because transition-of-coverage evidence can be necessary to assess continuity and avoid improper duplication.
11
Validates Provincial Program application/approval logic and required reasons
If provincial application made is No, require a non-empty reason explaining why no application was made. If provincial approval is No, require a decline reason; additionally, if the member’s province is Ontario and the drug is an EAP drug context, require an attachment indicator for EAP approval/denial documentation. If these validations fail, the request should be held because Manulife coverage is described as supplemental and provincial outcomes may be prerequisite to assessment.
12
Validates Patient Assistance Program details when enrollment is Yes
If Patient Assistance Program Enrollment is Yes, require case manager first/last name, phone, program name, and program ID; require case manager email if email is part of the contact workflow. Validate phone/email formats and ensure the ID is not blank and meets basic length/character constraints. If incomplete, return for correction because PAP coordination can affect access, cost-sharing, and case management communications.
13
Validates treatment administration location selection and dependent facility details
Ensure exactly one treatment administration location is selected (Home, MD office, Private Clinic, Hospital In-Patient, Hospital Out-patient). If location is not Home, require facility name, phone, and full address; if MD office is selected, require the 'MD office located in a hospital' Yes/No response, and if Yes require the administration area description. If these checks fail, flag because site-of-care impacts clinical review, billing, and potential preferred-provider routing.
14
Validates diagnosis selection is singular and triggers the correct clinical question set
Require exactly one diagnosis pathway to be selected: Type 2 Diabetes Mellitus (Initial), Type 2 Diabetes Mellitus (Renewal), or Any Other Diagnosis. Enforce that only the questions relevant to the selected pathway are answered, and that required questions within that pathway are completed. If invalid (multiple selected or none selected), block submission because clinical criteria and approval rules differ by pathway.
15
Validates Type 2 Diabetes clinical criteria logical consistency (Initial and Renewal)
For Initial criteria, require responses to all listed Yes/No questions and enforce key contradictions (e.g., if 'confirmed diagnosis' is No, the Initial pathway should not proceed; if 'used with other GLP-1 analogs' is Yes, flag as likely non-compliant with criteria). For Renewal criteria, require the continued benefit (HbA1c) response and enforce that if 'used with metformin' is No then 'documented intolerance/contraindication to metformin' must be Yes. If these checks fail, route to clinical review or reject as incomplete because inconsistent clinical answers undermine criteria-based adjudication.
16
Validates Ozempic dose limit and dosage field completeness
Require the 'Drug strength and dosage' free-text field to be non-empty and to include at least a numeric strength and unit plus frequency (e.g., mg and weekly/daily) using pattern checks. Cross-check the stated dose against the 'Will the dose exceed 2mg once weekly?' answer; if the text indicates >2 mg weekly but the checkbox says No (or vice versa), flag for correction. If validation fails, hold submission because dosing is central to safety, coverage rules, and correct application of the 2 mg once-weekly limit.
17
Validates drug history entries for date order, outcome selection, and rationale when none tried
For each drug therapy row that has a drug name, require a start date and ensure end date (if provided) is not earlier than start date; enforce yyyy/mmm format. Require at least one outcome checkbox (Intolerance or Inadequate/Suboptimal Response) for completed rows, and require a Yes/No selection for whether the medication will be continued. If no previous therapies are listed, require at least one rationale checkbox and a non-empty medical rationale explanation; otherwise, flag as incomplete because prior therapy history is needed to justify prior authorization.
18
Validates prescribing physician identity, licensing, and contact information completeness
Require physician first/last name, college/license number, specialty, practice address, and telephone number; validate license number against basic format/length rules and ensure phone/fax formats are valid. Ensure province and postal code are present and plausible for the practice address. If missing/invalid, reject or route to manual review because prescriber verification and contactability are essential for clinical assessment and compliance.
19
Ensures both physician and plan member signatures and dates are present and chronologically reasonable
Require physician signature and physician signature date, and require plan member signature and date signed, since both attestations are necessary for consent and clinical authorization. Validate that signature dates are valid and not in the future, and optionally flag if the plan member signature date precedes the physician signature date by an unusual margin (or vice versa) indicating potential form assembly issues. If signatures/dates are missing or invalid, the submission should be rejected because consent and certification requirements are not met.