If ASIMS is unavailable or the member is from another service, how should command authority notification be documented?

If ASIMS is unavailable or the member is from another service, how should command authority notification be documented?

• A. Via email to the commander's office.
• B. In the patient's medical record only.
• C. On a standard leave form.
• D. On Department of Defense DD Form 689, Individual Sick Slip, or a locally created form.

Answer: (D)

Notification of authority must be captured on a formal, auditable form so the command is officially informed and the record travels with the member. When ASIMS isn’t available or the member is from another service, this is done on the DD Form 689, Individual Sick Slip, or a locally created form. Using the DD 689 or a locally created document provides a standardized, official record that both medical and command channels can access, ensuring proper accountability across different systems or services. Relying on an email to the commander, recording only in the medical record, or using a generic leave form wouldn’t guarantee the formal, traceable notification that this process requires.

Notification of authority must be captured on a formal, auditable form so the command is officially informed and the record travels with the member. When ASIMS isn’t available or the member is from another service, this is done on the DD Form 689, Individual Sick Slip, or a locally created form. Using the DD 689 or a locally created document provides a standardized, official record that both medical and command channels can access, ensuring proper accountability across different systems or services. Relying on an email to the commander, recording only in the medical record, or using a generic leave form wouldn’t guarantee the formal, traceable notification that this process requires.