When a CEMP status becomes official correspondence

The status control is the starting point

A reviewer should not have to remember a separate letter workflow after making a decision. Selecting Under Review, Revision Requested, or Approved now starts the matching correspondence process. Ordinary administrative statuses continue to update normally, but these three consequential states cannot bypass the official letter and delivery safeguards.

Under Review confirms exactly what will happen

Before formal review begins, NextGenEM explains that proceeding will change the status, generate the Receipt and Review Acknowledgment PDF, and email the attachment to the submission originator. The reviewer sees the recipient, facility, anticipated review date, issuing official, and letter details before authorizing the action. Cancel leaves the record unchanged and sends nothing.

Revision Requested captures useful direction

Revision Requested opens a structured dialog for clear findings, an optional checklist item, plan page, or authority reference, the resubmission deadline, reviewer guidance, and contact information. The resulting email gives the originator a concise explanation while the attached Revisions Required PDF becomes the official retained notice.

Approval remains an authorized act

The approval confirmation identifies the approved facility and submission, approval date, next review date, any advisory conditions, and the authorized signer. Proceeding creates the formal Plan Approval PDF, updates the review status, and queues the complete branded email. Approval authority remains restricted to designated CEMP reviewers and administrators.

The PDF is the retained official record

Every issued letter is bound to the facility, submission, letter type, decision date, recipient, signer, and printed values. NextGenEM stores the exact PDF privately with a document number and SHA-256 checksum. An issued letter is never silently regenerated from later edits; a correction creates a superseding record while preserving the original audit history.

Delivery remains visible and recoverable

The correspondence history shows whether the email is Queued, Sent, Delivered, Failed, or Bounced. A failed or bounced delivery can be retried. If an originator reports that a sent or delivered letter was not received, staff can use a separate confirmed Resend action. Both paths reuse the same reviewed recipient, message, and immutable PDF, and record a new delivery attempt without creating a duplicate letter.

Contact Center carries the communication history

Every official letter now appears once in a linked CEMP Contact Center case with its document number, facility, recipient, retained PDF metadata, delivery state, failure reason, and event timeline. Existing letters are backfilled without duplication. Contact Center staff can triage the case and add private notes, while protected document access and every issue, retry, resend, or void action remain controlled by authorized CEMP reviewers in CEMP Review.

Provider evidence closes the loop

Each outgoing CEMP letter carries an immutable correlation identifier. Signature-verified Mailgun events automatically distinguish provider acceptance from confirmed delivery, temporary failure, permanent bounce, rejection, or complaint. Provider event IDs are deduplicated, recipient identity is checked, and a confirmed delivery cannot be overwritten by a contradictory late event. CEMP Review and Contact Center therefore show the same evidence-backed state rather than treating a queued job as proof of receipt.

One confirmation owns the whole decision

Once the reviewer confirms, NextGenEM issues the PDF, changes the status, queues the branded HTML email with a plain-text alternative and the actual PDF attachment, and records the actor and time. This keeps the operational decision, the official document, and the external communication synchronized without turning a tentative dropdown selection into an accidental notice.