AANP Certification Board
Not in scope for the I2C development.
Summary
The American Association of Nurse Practitioners (AANP) Certification Board (AANPCB) manages the certification of nurse practitioners. This document outlines the business requirements for four key processes handled by the AANP Certification Board: Search Site Integration, Nightly Automated Matching Process, Quarterly Reporting (Matching Members), and On-Demand Matching Process API. These processes aim to ensure efficient and streamlined management of certifications, membership verification, and reporting.
Requirements
Search Site Integration
Internal User Requirements
-
Access to Records:
- AANPCB should only have access to active individual members of AANP.
-
Filters and Criteria:
- Search by Member ID (PersonID), Email, First Name, and Last Name.
- Results should include only current AANP members.
-
User Interface Enhancements:
- Display Account Number, Name, City and State, Email, Membership Expiration Date, Full Address, and Last Modified Date of the Person record.
- Exclude the display of the Legacy Member Number.
- Remove the "(M)" after the AANP Account Number, as all results will only include members.
- Ignore the "View CE Tracker Data" option for these requirements.
-
Security and Access Control:
- Access should be restricted to certain AANPCB employees only.
- An audit trail should be maintained to track when AANPCB staff have logged in.
-
Performance Metrics:
- Response times should be comparable to other types of online search functionalities involving contact information.
Nightly Automated Matching Process
Internal User Requirements
-
Primary Data Sources:
- An API that connects to Aptify. AANPCB's system requests data for a user based on MemberNumber and LastName.
-
Matching Criteria and Rules:
- The process first tries to find an exact match using the member number.
- If no exact match is found, it looks for a partial match on the last name after cleaning and splitting the name into parts.
- Criteria include: Exact match by member number, partial last name match, and flexible matching using the
LIKEclause.
-
Handling Unmatched Records:
- Unmatched records should be flagged as "Not Found" in the API (404).
-
Notifications and Reports:
- Log usage and access attempts to the API.
-
Dependencies and Prerequisites:
- Access to the database (Aptify or Salesforce) is required.
Quarterly Reporting (Matching Members)
Internal User Requirements
-
Data Points and Metrics:
- AANPCB provides a list of their certification customers, including Name, AANP Member Number, and Email Address.
- Add an additional field, IsMember (a boolean value), to indicate if the individual is an AANP member.
-
Definition and Verification of Matching:
- Match criteria:
- Match by Member Number, First Name, Last Name.
- Match by Member Number, First Letter of First Name, Last Name.
- Match by Member Number, Email.
- Match by First Name, Last Name, Email (Email1, Email2, Email3).
- Match by First Letter of First Name, Last Name, Email (Email1, Email2, Email3).
- Match by Email Only (Email1, Email2, Email3).
- Match by Member Number, Last Name.
- Match criteria:
-
Formats or Templates:
- Reports should be generated in Excel format.
-
Stakeholders and Recipients:
- The primary recipient of the report is the AANPCB board.
-
Review and Approval Process:
- The Application Development Team is responsible for reviewing and approving the reports before they are finalized.
On-Demand Matching Process API
Internal User Requirements
-
Use Cases and Scenarios:
- The API is used for real-time verification of AANP membership status to provide AANPCB certification customers with discounts.
- Integrated with AANPCB's contact management system, allowing users to click a button that sends the first name, middle name, last name, and email address to verify AANP membership.
-
Endpoints and Functionalities:
- Endpoints for match requests and match status checks.
-
Input Parameters and Output:
- Input: First Name, Middle Name, Last Name, Email Address.
- Output: Match status, membership details if matched, including the discount eligibility.
-
Authentication and Security:
- API access should be secured using API keys or OAuth.
-
Performance and Scalability:
- The API should handle high volumes of requests with minimal latency, ensuring prompt response times.
Assumptions
- All Internal and External Users will be included in the Personas definition.
- Timelines will follow as outlined in each requirement.
References
This document provides a comprehensive overview and detailed requirements for managing AANPCB processes efficiently. If there are any additional details or further clarifications needed, please let me know.
Approvals / Signoffs
| Role | Name | Signature | Date |
|---|---|---|---|
| Technical Lead | Jeff Sikes | JS | 07/05/2024 |