About this site
Purpose
To consolidate the Austere Resuscitative Surgical Care (ARSC) framework around the Marine Corps Role 2 patient-flow construct, in a single web reference accessible without CAC credentials.
The audience is personnel of 1st Medical Battalion, 1st Marine Logistics Group. Joint and tri-service use is welcomed but additive — the content is framed in USMC terms first.
Authorship
Authored and maintained by CDR Brian S. Ford, MC, USN, Chief Medical Officer, 1st Medical Battalion. Contributions from other authors are credited per page where they apply.
Disclaimer
This site is a community professional reference compiled by CDR Brian S. Ford, MC, USN, drawing on publicly released doctrine. It is not an official publication of the Department of Defense, the Department of the Navy, the United States Marine Corps, or the Joint Trauma System. It carries no DoD endorsement. Always defer to current official doctrine and command policy. Where this site and current doctrine disagree, current doctrine prevails.
Report errors via the Contributing page.
Editorial principles
Cite, do not reproduce. Every doctrinal claim links to the canonical source. Quotations are kept short and attributed. The site does not republish CPGs, MCRPs, MCWPs, or JTS publications. It directs readers to them.
Service-neutral where the doctrine is joint; service-specific where the doctrine is service-specific. ARSC is a joint construct; STP, FRSS, and the holding capabilities are USMC-specific organization. The content reflects that distinction.
Currency. Each page carries a “last reviewed” date in its footer. Quarterly review cadence. Substantive updates appear in the Changelog.
Operational security
Every page passes an OPSEC review checklist before publication. The checklist excludes classified content, controlled unclassified content, personally identifying information, specific unit locations, planned operations, named exercise specifics not in open press, and AMAL line-item NSN data not already in publicly released NAVMED references. A copy of the checklist lives in the project repository.
Repository and licensing
Source content lives in a public Git repository. Submitted contributions are reviewed and merged by the maintainer. Content is licensed for non-commercial professional reference use; doctrinal citations remain the property of their authoring agencies.