  0 Table of Contents |
 1 Home |
   1.1 Changes |
| 1.2 Dependencies |
| 1.3 References |
| 1.4 Adapting Guidelines for Country use |
 1.5 License |
| 2 Business Requirements |
| 2.1 Concepts |
| 2.2 Generic Personas |
| 2.3 User Scenarios |
| 2.4 Business Processes |
| 2.5 Data Dictionary |
| 2.6 Decision-support logic |
| 2.7 Indicator and Performance Metrics |
| 2.8 System Requirements |
| 2.9 Functional Requirements |
| 2.10 Non-functional Requirements |
| 3 Data Models and Exchange |
| 3.1 System Actors |
| 3.2 Sequence Diagrams |
| 3.3 Transactions |
| 3.4 Indicators and Measures |
| 3.5 Codings |
| 4 Deployment |
| 4.1 Security and Privacy Considerations |
| 4.2 Testing |
| 4.3 Test Data |
| 4.4 Reference Implementations |
| 4.5 Trust Domains |
| 4.6 Downloads |
 5 Indices |
 5.1 Artifact Index |
| 5.1.1 Community health worker |
| 5.1.2 EIR staff |
| 5.1.3 EIR staff OR health worker |
| 5.1.4 Electronic immunization registry (EIR) staff |
| 5.1.5 Health worker |
| 5.1.6 Able to access the system at all levels/stores |
| 5.1.7 Accommodate loss of connectivity to hosted application (network may become unavailable while a user is in the process of submitting a form) |
| 5.1.8 Adjust display to fit small screens (e.g. mobile phones) |
| 5.1.9 Alert the user when navigating away from a form without saving |
| 5.1.10 Allow a task to be interrupted and resumed |
| 5.1.11 Allow admin user to request password reset |
| 5.1.12 Allow cascading user management and assignment of roles |
| 5.1.13 Allow each user to be assigned to one or more roles |
| 5.1.14 Allow for client devices with low bandwidth or irregular connectivity |
| 5.1.15 Allow for data exchange and efficient synchronization across multiple facilities and points of service when the internet is available, even when it is intermittent and slow |
| 5.1.16 Allow for flexible configurations based on the context of use, including the physical, regulatory and social environment |
| 5.1.17 Allow for maintenance of security updates |
| 5.1.18 Allow roles to be associated with specific geographical areas or health-care facilities |
| 5.1.19 Allow the administrator to establish access privileges and priorities |
| 5.1.20 Allow user to change their own password |
| 5.1.21 Allow user with permission to create a new user and temporary password |
| 5.1.22 Allow users to find features in two clicks or fewer |
| 5.1.23 Anonymize data that are exported from the system |
| 5.1.24 Assemble all needed materials for immunization session |
| 5.1.25 Automatically log out the user after a specified time of inactivity |
| 5.1.26 Be able to accommodate at least [x number of] concurrent users |
| 5.1.27 Be able to accommodate at least [x number of] health-care facilities |
| 5.1.28 Be able to be learned easily by end users and supervisors to meet specified goals of system effectiveness and efficiency |
| 5.1.29 Be able to provide continuity and access to data throughout changes in infrastructure (e.g. telecommunication, power) at the health-post level |
| 5.1.30 Be able to reliably perform tasks within appropriate time with resistance to failures or deadlocks |
| 5.1.31 Be built using technologies that enable local control, open competition and transparency of the code |
| 5.1.32 Be deployed in an environment subject to power loss |
| 5.1.33 Be reliable and robust (minimize the number of system crashes) |
| 5.1.34 Be user-friendly for people with low computer literacy |
| 5.1.35 Be well-documented, including known issues |
| 5.1.36 Capture or update client history |
| 5.1.37 Capture or update client history |
| 5.1.38 Check stock availability of recommended vaccines |
| 5.1.39 Check stock availability of recommended vaccines |
| 5.1.40 Check stock availability of recommended vaccines |
| 5.1.41 Comply with country's existing health information storage policies |
| 5.1.42 Comply with industry standards for data exchange |
| 5.1.43 Comply with industry standards for tracking and tracing of supplies |
| 5.1.44 Configure business rules in line with guidelines and standard operating procedures |
| 5.1.45 Configure error messages |
| 5.1.46 Configure the system centrally |
| 5.1.47 Create client record |
| 5.1.48 Create client record |
| 5.1.49 Create client record |
| 5.1.50 Create client record |
| 5.1.51 Create/update vaccination location record |
| 5.1.52 Define parameters for report |
| 5.1.53 Define parameters for report |
| 5.1.54 Define parameters for report |
| 5.1.55 Define parameters for report |
| 5.1.56 Define parameters for report |
| 5.1.57 Define/evaluate criteria |
| 5.1.58 Define/evaluate criteria |
| 5.1.59 Define/evaluate criteria |
| 5.1.60 Design software security protections to ensure system availability |
| 5.1.61 Determine if vaccines were missed |
| 5.1.62 Determine if vaccines were missed |
| 5.1.63 Determine required vaccination(s) |
| 5.1.64 Determine required vaccination(s) |
| 5.1.65 Determine required vaccination(s) |
| 5.1.66 Determine time for next visit (as needed) |
| 5.1.67 Determine vaccine(s) to be administered based on contraindications |
| 5.1.68 Determine vaccine(s) to be administered based on contraindications |
| 5.1.69 Dispose of waste |
| 5.1.70 Does client require a verifiable digital certificate? |
| 5.1.71 Emphasize ease of use and learnability to reduce training costs |
| 5.1.72 Enable a task to be cancelled and rolled back to previous state |
| 5.1.73 Enable access to the central system from all levels of the health system |
| 5.1.74 Enable backup of data so that information is recoverable in the event of a system or hardware failure |
| 5.1.75 Enable configuration to any national or subnational administrative structure or number of levels |
| 5.1.76 Enable earlier versions of a record to be recoverable |
| 5.1.77 Enable easy data collection, organization (predefined drop-down menus or searchable lists, radio buttons, check boxes) and dissemination |
| 5.1.78 Enable local control of operations |
| 5.1.79 Enable streamlined data collection, organization and dissemination |
| 5.1.80 Enable the system to detect incompatible versions of software running on different components |
| 5.1.81 Enable users to work offline and then synchronize data when data connection is available |
| 5.1.82 Evaluate vaccine event records |
| 5.1.83 Evaluate vaccine event records |
| 5.1.84 Evaluate vaccine event records |
| 5.1.85 Evaluate vaccine event records |
| 5.1.86 Evaluate vaccine event records |
| 5.1.87 Exchange actionable data between systems (need to enforce semantic interoperability) |
| 5.1.88 Flag client records for evaluation |
| 5.1.89 Flag client records for evaluation |
| 5.1.90 Flag client records for evaluation |
| 5.1.91 Focus on the mobile-user experience with secondary use of a computer |
| 5.1.92 Generate analysis of the use of different system features and reports |
| 5.1.93 Generate IDs that are unique across different locations or sites |
| 5.1.94 Generate list of clients |
| 5.1.95 Generate list of clients |
| 5.1.96 Generate list of clients |
| 5.1.97 Generate list of clients |
| 5.1.98 Generate list of clients |
| 5.1.99 Generate list of clients |
| 5.1.100 Generate list of clients who are due or overdue for vaccination |
| 5.1.101 Generate list of clients who are due or overdue for vaccination |
| 5.1.102 Generate list of clients who are due or overdue for vaccination |
| 5.1.103 Generate report |
| 5.1.104 Generate report |
| 5.1.105 Generate report |
| 5.1.106 Generate report |
| 5.1.107 Generate report |
| 5.1.108 Generate report of duplicate vaccine events |
| 5.1.109 Generate unique location identifier |
| 5.1.110 Generate verifiable digital certificate |
| 5.1.111 Get needed stock |
| 5.1.112 Have a source code audit against security threats |
| 5.1.113 Have a support process that tracks and documents bugs from discovery to resolution |
| 5.1.114 Have adequate support resources to ensure reusability, scalability and sustainability |
| 5.1.115 Have the ability to easily back up information |
| 5.1.116 Identify groups of vaccination events for evaluation |
| 5.1.117 Identify groups of vaccination events for evaluation |
| 5.1.118 Identify groups of vaccination events for evaluation |
| 5.1.119 Identify groups of vaccination events for evaluation |
| 5.1.120 Identify groups of vaccination events for evaluation |
| 5.1.121 Include an administrable content management system |
| 5.1.122 Link with insurance systems to verify eligibility and submit claims |
| 5.1.123 Lock a user out after a specified number of wrong password attempts |
| 5.1.124 Log access to data summaries, reports, analysis and visualization features |
| 5.1.125 Log access to views of individual client records |
| 5.1.126 Log all activities performed by the user, including date and time stamp |
| 5.1.127 Log all data and system errors |
| 5.1.128 Log exchange of data with other systems |
| 5.1.129 Maintain a transaction log history (system logins and logouts) |
| 5.1.130 Make efficient use of capabilities of lower-cost mobile devices |
| 5.1.131 Make efficient use of data communication time |
| 5.1.132 Mark as "not a duplicate" or "pending" |
| 5.1.133 Mark as "not a duplicate" or "pending" |
| 5.1.134 Merge records |
| 5.1.135 Merge records |
| 5.1.136 Merge records |
| 5.1.137 Merge records |
| 5.1.138 Monitor the client for any adverse reactions |
| 5.1.139 Notify a user if their account is locked due to wrong password attempts |
| 5.1.140 Notify the user of a password change to their account |
| 5.1.141 Notify the user to change their password the first time they log in |
| 5.1.142 Notify the user to regularly change their password |
| 5.1.143 Obtain vaccination location information |
| 5.1.144 Operate with open-source or third-party reporting tools |
| 5.1.145 Perform manual review |
| 5.1.146 Perform manual review |
| 5.1.147 Perform manual review |
| 5.1.148 Perform manual review |
| 5.1.149 Plan for follow-up directly or during outreach |
| 5.1.150 Prevent remembering username and password |
| 5.1.151 Prevent unauthorized access to clients' protected health information |
| 5.1.152 Prevent updates to the database occurring only partially (atomicity), which can cause greater problems than rejecting an entire submission of a form |
| 5.1.153 Produce list of potential duplicate records |
| 5.1.154 Promote easier acquisition by supporting a range of devices and form factors |
| 5.1.155 Protect against viruses and malware |
| 5.1.156 Protect system servers through the use of an internet firewall |
| 5.1.157 Provide a means to ensure confidentiality and privacy of personal health information |
| 5.1.158 Provide a mechanism to securely change a user's password |
| 5.1.159 Provide a search interface to reduce data-entry burden and improve accuracy on mobile devices |
| 5.1.160 Provide a unique version number for each version (all future updates and releases) |
| 5.1.161 Provide access from internet-enabled devices |
| 5.1.162 Provide access to data through application programming interfaces |
| 5.1.163 Provide an appropriate localized experience with both language and cultural translations |
| 5.1.164 Provide detailed architectural, operational and testing documentation |
| 5.1.165 Provide encrypted communication between components |
| 5.1.166 Provide feedback |
| 5.1.167 Provide flexible password control to align to national policy and standard operating procedures, including password format requirements |
| 5.1.168 Provide guidance to users to better support clinical guidelines and best clinical practices |
| 5.1.169 Provide informative error messages and tooltips |
| 5.1.170 Provide real-time messages such as "report processing" or "in progress" for transactions that affect the system performance |
| 5.1.171 Provide real-time response to transactions submitted by connected devices up to the configured national volume level |
| 5.1.172 Provide secure data transmission methods to prevent others from seeing data sent from one computer to another by using data encryption and private networks across public networks |
| 5.1.173 Provide the ability for allowed users to view confidential data |
| 5.1.174 Provide vaccination record |
| 5.1.175 Query client record |
| 5.1.176 Query client record |
| 5.1.177 Query client record |
| 5.1.178 Query client record |
| 5.1.179 Query client record |
| 5.1.180 Query client record |
| 5.1.181 Query client record |
| 5.1.182 Query client record |
| 5.1.183 Query client record |
| 5.1.184 Query client record |
| 5.1.185 Query client record |
| 5.1.186 Query client record |
| 5.1.187 Query client record |
| 5.1.188 Query client record |
| 5.1.189 Record all authentication violations |
| 5.1.190 Record details on planning sheet |
| 5.1.191 Record details on planning sheet |
| 5.1.192 Record details on planning sheet |
| 5.1.193 Record stock taken |
| 5.1.194 Record stock taken |
| 5.1.195 Record stock taken |
| 5.1.196 Record the necessary information to follow-up |
| 5.1.197 Record the necessary information to follow-up |
| 5.1.198 Report version number when saving data to the database |
| 5.1.199 Request additional information |
| 5.1.200 Request additional information |
| 5.1.201 Require each user to authenticate by role before gaining access to the system |
| 5.1.202 Reset a user's password in a secure manner |
| 5.1.203 Review past vaccination records to estimate vaccines needed |
| 5.1.204 Review past vaccination records to estimate vaccines needed |
| 5.1.205 Review past vaccination records to estimate vaccines needed |
| 5.1.206 Scalable to accommodate new demands |
| 5.1.207 Select notification method |
| 5.1.208 Select notification method |
| 5.1.209 Select the most accurate/suitable event record |
| 5.1.210 Select the most accurate/suitable event record |
| 5.1.211 Send client information to community health worker |
| 5.1.212 Send notifications |
| 5.1.213 Send notifications |
| 5.1.214 Send vaccination location registration notification |
| 5.1.215 Send vaccination location registration notification |
| 5.1.216 Show the number of records that are not yet synchronized |
| 5.1.217 Support ability to calculate values on behalf of user (eliminating need to add, subtract, multiply or divide) |
| 5.1.218 Support ability to recalculate the immunization scheduled or provide clinical decision support in the event that the client does not receive vaccines on time or has contraindications to their administration |
| 5.1.219 Support changes to organizational alignment of facilities and personnel |
| 5.1.220 Support data capacity considerations (including those for data transmission, storage and processing) for all users over the expected lifetime of the system |
| 5.1.221 Support definitions of unlimited roles and assigned levels of access, viewing, entry, editing and auditing |
| 5.1.222 Support extensibility and/or the ability to accept new services or functionality |
| 5.1.223 Support flexible models for data collection (e.g. including paper forms, web forms, SMS, barcode, etc.) |
| 5.1.224 Support privacy policies such as identifying who has access to the health data, and what data can be accessed |
| 5.1.225 Support real-time data-entry validation and feedback to prevent data-entry errors from being recorded |
| 5.1.226 Support repair or upgrade of a component in a running system |
| 5.1.227 Support reusability of the system source code |
| 5.1.228 Support the ability to store images and other unstructured data |
| 5.1.229 The ability for searches to include results that look or sound similar to the search term (phonetic search) |
| 5.1.230 The ability to associate a unique ID generated by another authority (local or global) to the record |
| 5.1.231 The ability to generate a barcode label to affix to the paper record |
| 5.1.232 The EIR system to be able to communicate with other systems (such as a national health management information system [HMIS] and Expanded Programme on Immunization [EPI]) to obtain vaccination locations information and other necessary information |
| 5.1.233 The notification to include specific details about upcoming immunization session dates and times or outreach dates and times as appropriate |
| 5.1.234 The search to match on partial information (such as partial birthdates) |
| 5.1.235 The system to allow barcode reading of stock taken |
| 5.1.236 The system to allow conversion of a temporary vaccination location to a permanent vaccination location |
| 5.1.237 The system to allow manual insertion of a new vaccination location not present in the NMFL in the EIR master list |
| 5.1.238 The system to allow me to print the stock order(s) to be fulfilled |
| 5.1.239 The system to allow search parameters configuration: mandatory fields, when partial information is acceptable, etc. |
| 5.1.240 The system to apply an authorised digital signature when necessary and appropriate |
| 5.1.241 The system to associate the context data for each entry (e.g. the vaccination location where the dose was given, the health worker administering it) |
| 5.1.242 The system to automatically flag client records as possible duplicates by marking them as pending for review |
| 5.1.243 The system to automatically flag event records as possible duplicates by marking them as pending for review |
| 5.1.244 The system to automatically identify changes in vaccination locations information, retrieved from other interconnected systems, and prompt for validation |
| 5.1.245 The system to automatically select the most accurate/suitable vaccination event to be used as the (primary or master) record |
| 5.1.246 The system to automatically send reminder notification to client or designated health worker (i.e. community health worker) based on the configured reminder parameters |
| 5.1.247 The system to be able to generate a report of duplicate vaccine events including the resolutions |
| 5.1.248 The system to be able to link a vaccination location’s NMFL identification (ID) with the corresponding EIR identifier |
| 5.1.249 The system to be able to merge records confirmed to be duplicates |
| 5.1.250 The system to be able to print reports on demand |
| 5.1.251 The system to be able to provide history of merged event records |
| 5.1.252 The system to be able to provide history of merged record for a given client |
| 5.1.253 The system to be able to undo a merge |
| 5.1.254 The system to be able to update vaccination location information |
| 5.1.255 The system to compare the list of needed antigens to the stock on hand and indicate if there is sufficient stock |
| 5.1.256 The system to determine vaccines due for a given client by considering relevant information, such as the age of the client, vaccine products, vaccines already given and predefined vaccine protocol |
| 5.1.257 The system to display a specific set of data related to the possible duplicated events (such as vaccine type, manufacturer, administration date, etc.) for manual review |
| 5.1.258 The system to display due date of the next vaccine |
| 5.1.259 The system to display stock availability of recommended vaccines |
| 5.1.260 The system to display the date the reminder/recall notice was sent to a client |
| 5.1.261 The system to display the expiry date of stock to ensure expired vaccines are not administered |
| 5.1.262 The system to display the information of the selected record |
| 5.1.263 The system to display the most probable matches at the top of the list |
| 5.1.264 The system to display vaccines due according to predefined vaccine protocol |
| 5.1.265 The system to enforce a minimal required data set for new registrations |
| 5.1.266 The system to ensure I have the most up-to-date vaccine protocols |
| 5.1.267 The system to flag a client as a defaulter after a configured number of reminders are sent |
| 5.1.268 The system to flag any vaccination location registered in the EIR that is not on the NMFL |
| 5.1.269 The system to generate a unique EIR identifier which may be linked to national ID or health ID |
| 5.1.270 The system to generate a unique identifier |
| 5.1.271 The system to generate automatically a list of possible duplicated vaccination events |
| 5.1.272 The system to generate report of missing information |
| 5.1.273 The system to group the defaulters by location and community health worker |
| 5.1.274 the system to identify any records that may have been imported from another system |
| 5.1.275 The system to identify changes made to the record for my confirmation before saving |
| 5.1.276 The system to include instructions on how to use EIR identifier |
| 5.1.277 The system to interface with National Master Facility List (NMFL) database to validate the EIR master list of vaccination locations |
| 5.1.278 The system to log each time a user prints a list of clients |
| 5.1.279 The system to log the actions performed on the reports |
| 5.1.280 The system to log updates of client information |
| 5.1.281 The system to maintain a tally of stock available at each location (e.g. stock available in the cold fridge at vaccination location, stock that is out for immunization session) |
| 5.1.282 The system to notify me of incomplete mandatory fields |
| 5.1.283 The system to offer the posibility of sending the generated report by email |
| 5.1.284 The system to prevent all records given an inactive or deceased status from being included in the list of clients for reminder/recall |
| 5.1.285 The system to produce and export reports in multiple formats (i.e. CSV, PDF) on demand |
| 5.1.286 The system to prompt a search for the client (check if it is already in the system) prior to starting a new record |
| 5.1.287 The system to prompt the user that a new vaccination event might already exist |
| 5.1.288 The system to provide a history of previous care (including previous vaccination records) |
| 5.1.289 The system to provide a immunization session materials checklist, which is a list of materials I would need for immunization session |
| 5.1.290 The system to provide range estimates for needed vaccines based on historical data (high and low ranges) |
| 5.1.291 The system to request confirmation if data is modified |
| 5.1.292 The system to retrieve and display, as a search result, a specific set of data (demographic information/photo/unique ID, etc. ) |
| 5.1.293 The system to return all potential matches based upon search criteria |
| 5.1.294 The system to schedule batching of duplicate record process |
| 5.1.295 The system to send a notification to the NMFL about a new vaccination location added to EIR |
| 5.1.296 The system to send EIR registration notification with EIR identifer to other systems |
| 5.1.297 The system to show me a preview of the report before printing |
| 5.1.298 The system to support a rules-based algorithm to evaluate duplicate events |
| 5.1.299 The system to support a rules-based algorithm to evaluate duplicate records |
| 5.1.300 The system to support an audit trail when event records are merged |
| 5.1.301 The system to support an audit trail when records are merged |
| 5.1.302 The system to support the process of sending a request for information |
| 5.1.303 The system to track that I have changed an existing record |
| 5.1.304 The system to track the number of reminders attempts (i.e. per client and total) |
| 5.1.305 The system to uniquely identify every client using a system generated unique identifier or an existing identifier (e.g. health care, national ID, health unique ID) |
| 5.1.306 The system to verify all required vaccination location information is complete |
| 5.1.307 The system to warn if required vaccine is not in stock |
| 5.1.308 To add client's health history (including previous vaccination records) |
| 5.1.309 To assign a community health worker to a client |
| 5.1.310 To associate a client with a vaccination location to generate a provider-based reminder/recall |
| 5.1.311 To be able to access the client records while reviewing the duplicates |
| 5.1.312 To be able to access the vaccination events while reviewing the duplicates |
| 5.1.313 To be able to check in the system the available stock at my vaccination location or at the local storage area/warehouse |
| 5.1.314 To be able to configure report parameters when creating new reports (period of time, inactive versus active clients, client's age, vaccine type, vaccine manufacturer, etc.) |
| 5.1.315 To be able to customize report parameters for error monitoring reports |
| 5.1.316 To be able to decide what information to keep from the duplicates |
| 5.1.317 To be able to enter comments for records marked as "not a duplicate" |
| 5.1.318 To be able to extend the search to external systems (such as a birth registry or a scheduling system) |
| 5.1.319 To be able to flag records as "not a duplicate" |
| 5.1.320 to be able to generate a list of clients according to defined parameters |
| 5.1.321 To be able to generate a report of clients who are inactive and disaggregate by the reason they are inactive |
| 5.1.322 To be able to include vaccination locations that may not be physical permanent facilities (such as temporary or pop-up clinics) |
| 5.1.323 To be able to indicate if a client is inactive, identified as either permanently or temporarily, with a reason (e.g. death, moved, refuses vaccine) |
| 5.1.324 To be able to manually flag duplicate records |
| 5.1.325 To be able to manually flag duplicate vaccination events |
| 5.1.326 To be able to manually initiate duplicates identification process |
| 5.1.327 To be able to merge manually duplicate records and decide what information to keep from the duplicates into a consolidated event record |
| 5.1.328 To be able to modify appropriate client data as needed |
| 5.1.329 To be able to modify the business rules used for identifying duplicate client records |
| 5.1.330 to be able to modify the business rules used for identifying vaccination events duplicates |
| 5.1.331 To be able to quickly access information regarding any contraindications by antigen |
| 5.1.332 To be able to schedule routine reports (specific date/time, daily, weekly, etc.) |
| 5.1.333 To be able to select report parameters when creating vaccination coverage reports (i.e. by vaccine, by dose, by age, by area, by condition, by vaccine manufacturer, etc) |
| 5.1.334 To be able to select what information a report shows (i.e. display options, summary versus detail report, sort options) |
| 5.1.335 To be able to set a specific inactivity time frame for temporarily inactive clients (e.g. temporarily lost residence, crop harvest season) |
| 5.1.336 To be able to view simultaneously potential duplicate records |
| 5.1.337 To be able to view simultaneously potential duplicate records |
| 5.1.338 To be alerted of any relevant potential contraindications for the vaccine (e.g. based on age, previous allergic reactions, etc.) |
| 5.1.339 To be prompted for any data required to produce a digital vaccine certificate |
| 5.1.340 To be prompted to ask client if they want a digital vaccination certificate where appropriate |
| 5.1.341 To display a list of clients due for specific planned outreach and immunization sessions, based on area |
| 5.1.342 To document why a vaccine was not given |
| 5.1.343 To enter additional search criteria if there are multiple possible matches |
| 5.1.344 To export a list of clients for follow-up |
| 5.1.345 To find client records using barcodes that contain the client ID |
| 5.1.346 To flag when there is a change of address and a new client has been added to another catchment area |
| 5.1.347 To identify, by checking the information in the system, all clients that are due (or overdue) for vaccination by the next immunization session date |
| 5.1.348 To print a list of clients requiring follow-up |
| 5.1.349 To print the list of clients generated according to defined parameters |
| 5.1.350 To print the list of necessary antigens and accessories (e.g. syringes, wipes) based on projected need |
| 5.1.351 To produce a list of clients who missed their vaccine for each antigen, along with their location and personal information |
| 5.1.352 To record additional vaccinations, even those that are not included in the national vaccination schedule |
| 5.1.353 To record any significant observations (such as reaction) that may be specific to that client |
| 5.1.354 To record in the system the results of the follow-up |
| 5.1.355 To record reason vaccine was missed |
| 5.1.356 To record stock removed from cold storage and taken to immunization session |
| 5.1.357 To search for a client using at least two identifying information |
| 5.1.358 To search for the client record given some demographic information |
| 5.1.359 To search with wild cards (using a symbol to replace one or more characters) |
| 5.1.360 To select one or more notification methods (e.g. automated telephone calls [i.e. robocall], text message, letter, email, community health worker notification, home visits) |
| 5.1.361 To select reminder parameters. May include but not limited to, age range, vaccine type(s), vaccine schedules, geographic area, number of days overdue, number of reminders, etc. |
| 5.1.362 To select the place of birth from a standardized list of locations |
| 5.1.363 To select the vaccination location of the client from a list of locations |
| 5.1.364 To send list of clients who missed immunization sessions by email or SMS to the community health worker |
| 5.1.365 To set client's preferred contact method |
| 5.1.366 To sort the list of needed vaccines by antigen |
| 5.1.367 To specify thresholds for a client to qualify as requiring follow-up, based on the national immunization guidelines |
| 5.1.368 To update client information such as including change of address (moved permanently or temporarily) |
| 5.1.369 To update clients’ vaccination record with all relevant information (i.e. date, dose, batch number, lot number, vaccine type, vaccine vial monitor status) |
| 5.1.370 To update stock record |
| 5.1.371 To validate data against the vaccine schedule (Note: Can use the vaccine schedule to best schedule reminders/recall for series vaccinations) |
| 5.1.372 Trace and record changes to data taken by the system and by users (update/delete/add/access) |
| 5.1.373 Transmit information in a language (script or voice) that is understood by the user population |
| 5.1.374 Update client record |
| 5.1.375 Update client record |
| 5.1.376 Update client record |
| 5.1.377 Update client record |
| 5.1.378 Update client record |
| 5.1.379 Update client record |
| 5.1.380 Update record to document reason/lost follow-up |
| 5.1.381 Update record to document reason/lost follow-up |
| 5.1.382 Update record to document reason/lost follow-up |
| 5.1.383 Update record to document reason/lost follow-up |
| 5.1.384 Update record to document reason/lost follow-up |
| 5.1.385 Update record to document reason/lost follow-up |
| 5.1.386 Update vaccination event records |
| 5.1.387 Update vaccination event records |
| 5.1.388 Update/add new vaccination location |
| 5.1.389 Update/add new vaccination location |
| 5.1.390 Update/add new vaccination location |
| 5.1.391 Update/add new vaccination location |
| 5.1.392 Use a database that can scale to support projected transaction volume |
| 5.1.393 Use industry-standard user interface practices and apply them consistently throughout the system |
| 5.1.394 Use open standards to promote interoperability |
| 5.1.395 Validate a unique identifier when system is offline |
| 5.1.396 Validate against national master facility list |
| 5.1.397 Validate against national master facility list |
| 5.1.398 Validate against national master facility list |
| 5.1.399 Validate client details |
| 5.1.400 Validate client details |
| 5.1.401 Validate client details |
| 5.1.402 Validate client details |
| 5.1.403 Validate client details |
| 5.1.404 Validate client details |
| 5.1.405 Validate client details |
| 5.1.406 Validate client details |
| 5.1.407 Verify information for additional data |
| 5.1.408 Verify information for additional data |
| 5.1.409 Verify information for additional data |
| 5.1.410 Warn user if no valid back-up for more than a predefined number of days |
| 5.1.411 Functional Requirement Categories |
| 5.1.412 Functional Requirements Business Processes |
| 5.1.413 Functional Requirement Categories |
| 5.1.414 Functional Requirements Business Processes |
| 5.1.415 LM.IMMZ.FXNREQ.001.A |
| 5.1.416 LM.IMMZ.FXNREQ.002.A |
| 5.1.417 LM.IMMZ.FXNREQ.003.A |
| 5.1.418 LM.IMMZ.FXNREQ.004.A |
| 5.1.419 LM.IMMZ.FXNREQ.005.A |
| 5.1.420 LM.IMMZ.FXNREQ.006.A |
| 5.1.421 LM.IMMZ.FXNREQ.007.A |
| 5.1.422 LM.IMMZ.FXNREQ.008.A |
| 5.1.423 LM.IMMZ.FXNREQ.009.A |
| 5.1.424 LM.IMMZ.FXNREQ.010.A |
| 5.1.425 LM.IMMZ.FXNREQ.011.A |
| 5.1.426 LM.IMMZ.FXNREQ.012.A |
| 5.1.427 LM.IMMZ.FXNREQ.013.A |
| 5.1.428 LM.IMMZ.FXNREQ.014.A |
| 5.1.429 LM.IMMZ.FXNREQ.015.A |
| 5.1.430 LM.IMMZ.FXNREQ.016.A |
| 5.1.431 LM.IMMZ.FXNREQ.017.A |
| 5.1.432 LM.IMMZ.FXNREQ.018.B |
| 5.1.433 LM.IMMZ.FXNREQ.019.B |
| 5.1.434 LM.IMMZ.FXNREQ.020.B |
| 5.1.435 LM.IMMZ.FXNREQ.021.B |
| 5.1.436 LM.IMMZ.FXNREQ.022.B |
| 5.1.437 LM.IMMZ.FXNREQ.023.B |
| 5.1.438 LM.IMMZ.FXNREQ.030.B |
| 5.1.439 LM.IMMZ.FXNREQ.031.B |
| 5.1.440 LM.IMMZ.FXNREQ.032.B |
| 5.1.441 LM.IMMZ.FXNREQ.033.B |
| 5.1.442 LM.IMMZ.FXNREQ.034.B |
| 5.1.443 LM.IMMZ.FXNREQ.035.C |
| 5.1.444 LM.IMMZ.FXNREQ.036.C |
| 5.1.445 LM.IMMZ.FXNREQ.037.C |
| 5.1.446 LM.IMMZ.FXNREQ.038.C |
| 5.1.447 LM.IMMZ.FXNREQ.039.C |
| 5.1.448 LM.IMMZ.FXNREQ.040.C |
| 5.1.449 LM.IMMZ.FXNREQ.041.C |
| 5.1.450 LM.IMMZ.FXNREQ.042.C |
| 5.1.451 LM.IMMZ.FXNREQ.043.C |
| 5.1.452 LM.IMMZ.FXNREQ.044.C |
| 5.1.453 LM.IMMZ.FXNREQ.045.C |
| 5.1.454 LM.IMMZ.FXNREQ.046.C |
| 5.1.455 LM.IMMZ.FXNREQ.047.C |
| 5.1.456 LM.IMMZ.FXNREQ.048.C |
| 5.1.457 LM.IMMZ.FXNREQ.049.C |
| 5.1.458 LM.IMMZ.FXNREQ.050.C |
| 5.1.459 LM.IMMZ.FXNREQ.051.C |
| 5.1.460 LM.IMMZ.FXNREQ.052.C |
| 5.1.461 LM.IMMZ.FXNREQ.053.C |
| 5.1.462 LM.IMMZ.FXNREQ.054.C |
| 5.1.463 LM.IMMZ.FXNREQ.055.C |
| 5.1.464 LM.IMMZ.FXNREQ.056.C |
| 5.1.465 LM.IMMZ.FXNREQ.057.C |
| 5.1.466 LM.IMMZ.FXNREQ.058.C |
| 5.1.467 LM.IMMZ.FXNREQ.059.C |
| 5.1.468 LM.IMMZ.FXNREQ.060.C |
| 5.1.469 LM.IMMZ.FXNREQ.061.D |
| 5.1.470 LM.IMMZ.FXNREQ.062.D |
| 5.1.471 LM.IMMZ.FXNREQ.063.D |
| 5.1.472 LM.IMMZ.FXNREQ.064.D |
| 5.1.473 LM.IMMZ.FXNREQ.065.D |
| 5.1.474 LM.IMMZ.FXNREQ.066.D |
| 5.1.475 LM.IMMZ.FXNREQ.067.D |
| 5.1.476 LM.IMMZ.FXNREQ.068.D |
| 5.1.477 LM.IMMZ.FXNREQ.069.D |
| 5.1.478 LM.IMMZ.FXNREQ.070.D |
| 5.1.479 LM.IMMZ.FXNREQ.071.D |
| 5.1.480 LM.IMMZ.FXNREQ.072.D |
| 5.1.481 LM.IMMZ.FXNREQ.073.D |
| 5.1.482 LM.IMMZ.FXNREQ.074.D |
| 5.1.483 LM.IMMZ.FXNREQ.075.D |
| 5.1.484 LM.IMMZ.FXNREQ.076.D |
| 5.1.485 LM.IMMZ.FXNREQ.077.D |
| 5.1.486 LM.IMMZ.FXNREQ.078.D |
| 5.1.487 LM.IMMZ.FXNREQ.080.D |
| 5.1.488 LM.IMMZ.FXNREQ.081.D |
| 5.1.489 LM.IMMZ.FXNREQ.082.D |
| 5.1.490 LM.IMMZ.FXNREQ.083.D |
| 5.1.491 LM.IMMZ.FXNREQ.084.E |
| 5.1.492 LM.IMMZ.FXNREQ.085.E |
| 5.1.493 LM.IMMZ.FXNREQ.086.E |
| 5.1.494 LM.IMMZ.FXNREQ.087.E |
| 5.1.495 LM.IMMZ.FXNREQ.088.E |
| 5.1.496 LM.IMMZ.FXNREQ.089.E |
| 5.1.497 LM.IMMZ.FXNREQ.090.E |
| 5.1.498 LM.IMMZ.FXNREQ.091.E |
| 5.1.499 LM.IMMZ.FXNREQ.092.E |
| 5.1.500 LM.IMMZ.FXNREQ.093.E |
| 5.1.501 LM.IMMZ.FXNREQ.094.E |
| 5.1.502 LM.IMMZ.FXNREQ.095.E |
| 5.1.503 LM.IMMZ.FXNREQ.096.E |
| 5.1.504 LM.IMMZ.FXNREQ.097.F |
| 5.1.505 LM.IMMZ.FXNREQ.098.F |
| 5.1.506 LM.IMMZ.FXNREQ.099.F |
| 5.1.507 LM.IMMZ.FXNREQ.100.F |
| 5.1.508 LM.IMMZ.FXNREQ.101.F |
| 5.1.509 LM.IMMZ.FXNREQ.102.F |
| 5.1.510 LM.IMMZ.FXNREQ.103.F |
| 5.1.511 LM.IMMZ.FXNREQ.104.F |
| 5.1.512 LM.IMMZ.FXNREQ.105.F |
| 5.1.513 LM.IMMZ.FXNREQ.106.F |
| 5.1.514 LM.IMMZ.FXNREQ.107.F |
| 5.1.515 LM.IMMZ.FXNREQ.108.F |
| 5.1.516 LM.IMMZ.FXNREQ.109.F |
| 5.1.517 LM.IMMZ.FXNREQ.110.F |
| 5.1.518 LM.IMMZ.FXNREQ.111.F |
| 5.1.519 LM.IMMZ.FXNREQ.112.F |
| 5.1.520 LM.IMMZ.FXNREQ.113.G |
| 5.1.521 LM.IMMZ.FXNREQ.114.G |
| 5.1.522 LM.IMMZ.FXNREQ.115.G |
| 5.1.523 LM.IMMZ.FXNREQ.116.G |
| 5.1.524 LM.IMMZ.FXNREQ.117.G |
| 5.1.525 LM.IMMZ.FXNREQ.118.G |
| 5.1.526 LM.IMMZ.FXNREQ.119.G |
| 5.1.527 LM.IMMZ.FXNREQ.120.G |
| 5.1.528 LM.IMMZ.FXNREQ.121.G |
| 5.1.529 LM.IMMZ.FXNREQ.122.G |
| 5.1.530 LM.IMMZ.FXNREQ.123.G |
| 5.1.531 LM.IMMZ.FXNREQ.124.G |
| 5.1.532 LM.IMMZ.FXNREQ.125.G |
| 5.1.533 LM.IMMZ.FXNREQ.126.G |
| 5.1.534 LM.IMMZ.FXNREQ.127.H |
| 5.1.535 LM.IMMZ.FXNREQ.128.H |
| 5.1.536 LM.IMMZ.FXNREQ.129.H |
| 5.1.537 LM.IMMZ.FXNREQ.130.H |
| 5.1.538 LM.IMMZ.FXNREQ.131.H |
| 5.1.539 LM.IMMZ.FXNREQ.132.H |
| 5.1.540 LM.IMMZ.FXNREQ.133.H |
| 5.1.541 LM.IMMZ.FXNREQ.134.H |
| 5.1.542 LM.IMMZ.FXNREQ.135.H |
| 5.1.543 LM.IMMZ.FXNREQ.136.H |
| 5.1.544 LM.IMMZ.FXNREQ.137.H |
| 5.1.545 LM.IMMZ.FXNREQ.138.H |
| 5.1.546 LM.IMMZ.FXNREQ.139.H |
| 5.1.547 LM.IMMZ.FXNREQ.140.H |
| 5.1.548 LM.IMMZ.FXNREQ.141.H |
| 5.1.549 LM.IMMZ.FXNREQ.142.I |
| 5.1.550 LM.IMMZ.FXNREQ.143.I |
| 5.1.551 LM.IMMZ.FXNREQ.144.I |
| 5.1.552 LM.IMMZ.FXNREQ.145.I |
| 5.1.553 LM.IMMZ.FXNREQ.146.I |
| 5.1.554 LM.IMMZ.FXNREQ.147.I |
| 5.1.555 LM.IMMZ.FXNREQ.148.I |
| 5.1.556 LM.IMMZ.FXNREQ.149.I |
| 5.1.557 LM.IMMZ.FXNREQ.150.I |
| 5.1.558 LM.IMMZ.FXNREQ.151.I |
| 5.1.559 LM.IMMZ.NFXNREQ.001 |
| 5.1.560 LM.IMMZ.NFXNREQ.002 |
| 5.1.561 LM.IMMZ.NFXNREQ.003 |
| 5.1.562 LM.IMMZ.NFXNREQ.004 |
| 5.1.563 LM.IMMZ.NFXNREQ.005 |
| 5.1.564 LM.IMMZ.NFXNREQ.006 |
| 5.1.565 LM.IMMZ.NFXNREQ.007 |
| 5.1.566 LM.IMMZ.NFXNREQ.008 |
| 5.1.567 LM.IMMZ.NFXNREQ.009 |
| 5.1.568 LM.IMMZ.NFXNREQ.010 |
| 5.1.569 LM.IMMZ.NFXNREQ.011 |
| 5.1.570 LM.IMMZ.NFXNREQ.012 |
| 5.1.571 LM.IMMZ.NFXNREQ.013 |
| 5.1.572 LM.IMMZ.NFXNREQ.014 |
| 5.1.573 LM.IMMZ.NFXNREQ.015 |
| 5.1.574 LM.IMMZ.NFXNREQ.016 |
| 5.1.575 LM.IMMZ.NFXNREQ.017 |
| 5.1.576 LM.IMMZ.NFXNREQ.018 |
| 5.1.577 LM.IMMZ.NFXNREQ.019 |
| 5.1.578 LM.IMMZ.NFXNREQ.020 |
| 5.1.579 LM.IMMZ.NFXNREQ.021 |
| 5.1.580 LM.IMMZ.NFXNREQ.022 |
| 5.1.581 LM.IMMZ.NFXNREQ.023 |
| 5.1.582 LM.IMMZ.NFXNREQ.024 |
| 5.1.583 LM.IMMZ.NFXNREQ.025 |
| 5.1.584 LM.IMMZ.NFXNREQ.026 |
| 5.1.585 LM.IMMZ.NFXNREQ.027 |
| 5.1.586 LM.IMMZ.NFXNREQ.028 |
| 5.1.587 LM.IMMZ.NFXNREQ.029 |
| 5.1.588 LM.IMMZ.NFXNREQ.030 |
| 5.1.589 LM.IMMZ.NFXNREQ.031 |
| 5.1.590 LM.IMMZ.NFXNREQ.032 |
| 5.1.591 LM.IMMZ.NFXNREQ.033 |
| 5.1.592 LM.IMMZ.NFXNREQ.034 |
| 5.1.593 LM.IMMZ.NFXNREQ.035 |
| 5.1.594 LM.IMMZ.NFXNREQ.036 |
| 5.1.595 LM.IMMZ.NFXNREQ.037 |
| 5.1.596 LM.IMMZ.NFXNREQ.038 |
| 5.1.597 LM.IMMZ.NFXNREQ.039 |
| 5.1.598 LM.IMMZ.NFXNREQ.040 |
| 5.1.599 LM.IMMZ.NFXNREQ.041 |
| 5.1.600 LM.IMMZ.NFXNREQ.042 |
| 5.1.601 LM.IMMZ.NFXNREQ.043 |
| 5.1.602 LM.IMMZ.NFXNREQ.044 |
| 5.1.603 LM.IMMZ.NFXNREQ.045 |
| 5.1.604 LM.IMMZ.NFXNREQ.046 |
| 5.1.605 LM.IMMZ.NFXNREQ.047 |
| 5.1.606 LM.IMMZ.NFXNREQ.048 |
| 5.1.607 LM.IMMZ.NFXNREQ.049 |
| 5.1.608 LM.IMMZ.NFXNREQ.050 |
| 5.1.609 LM.IMMZ.NFXNREQ.051 |
| 5.1.610 LM.IMMZ.NFXNREQ.052 |
| 5.1.611 LM.IMMZ.NFXNREQ.053 |
| 5.1.612 LM.IMMZ.NFXNREQ.054 |
| 5.1.613 LM.IMMZ.NFXNREQ.055 |
| 5.1.614 LM.IMMZ.NFXNREQ.056 |
| 5.1.615 LM.IMMZ.NFXNREQ.057 |
| 5.1.616 LM.IMMZ.NFXNREQ.058 |
| 5.1.617 LM.IMMZ.NFXNREQ.059 |
| 5.1.618 LM.IMMZ.NFXNREQ.060 |
| 5.1.619 LM.IMMZ.NFXNREQ.061 |
| 5.1.620 LM.IMMZ.NFXNREQ.062 |
| 5.1.621 LM.IMMZ.NFXNREQ.063 |
| 5.1.622 LM.IMMZ.NFXNREQ.064 |
| 5.1.623 LM.IMMZ.NFXNREQ.065 |
| 5.1.624 LM.IMMZ.NFXNREQ.066 |
| 5.1.625 LM.IMMZ.NFXNREQ.067 |
| 5.1.626 LM.IMMZ.NFXNREQ.068 |
| 5.1.627 LM.IMMZ.NFXNREQ.069 |
| 5.1.628 LM.IMMZ.NFXNREQ.070 |
| 5.1.629 LM.IMMZ.NFXNREQ.071 |
| 5.1.630 LM.IMMZ.NFXNREQ.072 |
| 5.1.631 LM.IMMZ.NFXNREQ.073 |
| 5.1.632 LM.IMMZ.NFXNREQ.074 |
| 5.1.633 LM.IMMZ.NFXNREQ.075 |
| 5.1.634 LM.IMMZ.NFXNREQ.076 |
| 5.1.635 LM.IMMZ.NFXNREQ.077 |
| 5.1.636 LM.IMMZ.NFXNREQ.078 |
| 5.1.637 LM.IMMZ.NFXNREQ.079 |
| 5.1.638 LM.IMMZ.NFXNREQ.080 |
| 5.1.639 LM.IMMZ.NFXNREQ.081 |
| 5.1.640 LM.IMMZ.NFXNREQ.082 |
| 5.1.641 LM.IMMZ.NFXNREQ.083 |
| 5.1.642 LM.IMMZ.NFXNREQ.084 |
| 5.1.643 LM.IMMZ.NFXNREQ.085 |
| 5.1.644 LM.IMMZ.NFXNREQ.086 |
| 5.1.645 LM.IMMZ.NFXNREQ.087 |
| 5.1.646 LM.IMMZ.NFXNREQ.088 |
| 5.1.647 LM.IMMZ.NFXNREQ.089 |
| 5.1.648 LM.IMMZ.NFXNREQ.090 |
| 5.1.649 LM.IMMZ.NFXNREQ.091 |
| 5.1.650 LM.IMMZ.NFXNREQ.092 |
| 5.1.651 LM.IMMZ.NFXNREQ.093 |
| 5.1.652 LM.IMMZ.NFXNREQ.094 |
| 5.1.653 LM.IMMZ.NFXNREQ.095 |
| 5.1.654 LM.IMMZ.NFXNREQ.096 |
| 5.1.655 LM.IMMZ.NFXNREQ.097 |
| 5.1.656 LM.IMMZ.NFXNREQ.098 |
| 5.1.657 LM.IMMZ.NFXNREQ.099 |
| 5.1.658 LM.IMMZ.NFXNREQ.100 |
| 5.1.659 LM.IMMZ.NFXNREQ.101 |
| 5.1.660 LM.IMMZ.NFXNREQ.102 |
| 5.1.661 LM.IMMZ.NFXNREQ.103 |
| 5.1.662 LM.IMMZ.NFXNREQ.104 |
| 5.1.663 LM.IMMZ.NFXNREQ.105 |
| 5.1.664 LM.IMMZ.NFXNREQ.106 |
| 5.1.665 LM.IMMZ.NFXNREQ.107 |
| 5.1.666 LM.IMMZ.NFXNREQ.108 |
| 5.1.667 LM.IMMZ.NFXNREQ.109 |
| 5.1.668 LM.IMMZ.NFXNREQ.110 |
| 5.1.669 LM.IMMZ.NFXNREQ.111 |
| 5.1.670 LM.IMMZ.NFXNREQ.112 |
| 5.1.671 LM.IMMZ.NFXNREQ.113 |
| 5.1.672 LM.IMMZ.NFXNREQ.114 |
| 5.1.673 LM.IMMZ.NFXNREQ.115 |
| 5.1.674 LM.IMMZ.NFXNREQ.116 |
| 5.1.675 LM.IMMZ.NFXNREQ.117 |
| 5.2 Mappings |