ACEMAPP Process for Coordinating Rotations Among Schools, Sites, and Students
This guide outlines the essential steps for coordinating clinical rotations among schools, clinical sites, and students through ACEMAPP. It details the partnership request process, student and faculty account management, rotation approval, compliance monitoring, and site access authorization. For detailed instructions on how to complete each step, please refer to the specific member guides tailored for students, faculty, schools, and clinical sites.
| Role |
Action |
Notes / Practical Tips |
| |
Step 1: Partnership Request and Approval Process |
Purpose: Establish formal partnerships between schools and clinical sites to enable student rotations. |
| School |
Requests to establish a partnership with clinical sites only if programs align and a formal agreement with the partner is already established. |
Contact ACEMAPP support if you are unable to find the entity you'd like to request partnership using the Partnership Directory. |
| ACEMAPP |
Notifies the clinical site of the partnership request. |
ACEMAPP acts as the communication facilitator between schools and clinical sites. |
| Clinical Site |
Approves or denies the partnership request. |
Clinical site reviews the request based on shared agreement and program compatibility. |
| ACEMAPP |
Notifies the school of the clinical site’s decision. |
Immediate notification ensures the school can act accordingly. |
|
| |
Step 2: Creation and Affiliation of Student and Faculty Accounts |
Purpose: Ensure all participants have verified ACEMAPP accounts connected to the correct program. |
| School |
Creates or affiliates student and faculty accounts in ACEMAPP to connect with their program. |
This establishes the necessary member profiles to participate in rotations. |
| ACEMAPP |
Sends verification and login information to new members; for existing students, sends affiliation requests. |
Ensures all members have access and properly link their accounts to the correct school/program. |
| Student/Faculty |
Verifies email and logs in to complete their profile to meet school requirements; approves affiliation requests. |
Existing users must approve affiliation for the school to track their compliance and rotations. |
| |
Step 3: Submission and Review of Rotation Requests |
Purpose: Submit rotation requests to clinical sites and obtain approval for student participation. |
| School |
After partnership approval, creates a rotation request with the clinical site; sets status to “Pending” for review. |
The “Pending” status signals the clinical site to evaluate the rotation request. |
| ACEMAPP |
Notifies the clinical site of the pending rotation request. |
Keeps clinical site informed to prompt timely review. |
| Clinical Site |
Reviews rotation request and either approves, denies, or marks it as “Needs Info.” |
Provides feedback or requests additional information if necessary before final decision. |
| ACEMAPP |
Notifies the school of the clinical site’s rotation decision. |
Enables the school to proceed based on site’s approval or required adjustments. |
| |
Step 4: Assigning Students and Faculty to Approved Rotations |
Purpose: Grant access to rotations and ensure participants can complete necessary onboarding. |
| School |
Assigns students and faculty members to the approved rotation. |
This step enables member access to clinical site requirements and onboarding.. |
| ACEMAPP |
Notifies assigned students and faculty of their rotation assignment. |
Ensures participants are aware of their clinical responsibilities. |
| Student/Faculty |
Logs in to complete clinical requirements and onboarding steps to demonstrate compliance. |
Compliance is mandatory before participating in clinical rotations |
| |
Step 5: Monitoring Compliance and Reviewing Clinical Requirements |
Purpose: Track student progress and ensure ongoing compliance with clinical site requirements. |
| School |
Reviews required documents submitted by students and monitors ongoing compliance. |
Schools oversee that students meet all clinical site requirements throughout the rotation. |
| Student/Faculty |
Receives weekly reminders from ACEMAPP about incomplete clinical requirements.. |
Automated reminders help keep students on track. |
| ACEMAPP |
Sends the roster of compliant students to clinical sites for approved rotations. |
Only students who meet requirements are included on the roster sent to clinical sites. |
| |
Step 6: Final Compliance Verification and Roster Approval |
Purpose: Ensure only fully compliant students are eligible for rotations. |
| Clinical Site |
Reviews the roster to ensure all listed students meet compliance requirements. |
Final verification by the clinical site to confirm student eligibility for rotation participation. |
| |
Step 7: Student and Faculty Site Access Authorization |
Purpose: Grant access to clinical sites once all compliance requirements are met. |
| Student/Faculty |
Allowed to begin clinical rotation once all compliance requirements are met and before the clinical site’s specified deadline. |
Ensures only fully compliant members are granted access to the clinical site, maintaining safety and regulatory standards. |
A rotation is a scheduled clinical experience.
The completion of all required items in ACEMAPP.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
A rotation is a scheduled clinical experience.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
An Entity is a School, Clinical Site, High School, Company, etc.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
An Affiliation is a connection between a Member and an Entity.
Affiliations define Member Types and often include Graduation or End Dates.
The Profile allows you to enter and edit personal information in ACEMAPP.
A rotation is a scheduled clinical experience.
An Affiliation is a connection between a Member and an Entity.
Affiliations define Member Types and often include Graduation or End Dates.
An Affiliation is a connection between a Member and an Entity.
Affiliations define Member Types and often include Graduation or End Dates.
The Profile allows you to enter and edit personal information in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
An Affiliation is a connection between a Member and an Entity.
Affiliations define Member Types and often include Graduation or End Dates.
The completion of all required items in ACEMAPP.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
The connection between Entities in ACEMAPP.
An active Partnership between two entities is needed to create a rotation in ACEMAPP.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A rotation is a scheduled clinical experience.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
A rotation is a scheduled clinical experience.
The completion of all required items in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
The completion of all required items in ACEMAPP.
A rotation is a scheduled clinical experience.
The completion of all required items in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
The completion of all required items in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
A rotation is a scheduled clinical experience.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
The roster tracks members assigned to a rotation and gives the clinical site access to view the rotation information, member compliance records, and member profile data.
A rotation is a scheduled clinical experience.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
The roster tracks members assigned to a rotation and gives the clinical site access to view the rotation information, member compliance records, and member profile data.
The completion of all required items in ACEMAPP.
The roster tracks members assigned to a rotation and gives the clinical site access to view the rotation information, member compliance records, and member profile data.
The completion of all required items in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
The roster tracks members assigned to a rotation and gives the clinical site access to view the rotation information, member compliance records, and member profile data.
A rotation is a scheduled clinical experience.
The completion of all required items in ACEMAPP.
A requirement is an item a member may need to complete based on their affiliation to an entity or rotation assignment.
A rotation is a scheduled clinical experience.
