Data The system must allow for multiple field entries Components for fields, including but not limited to address, N.2 phone number, guardian and race. Functional Requirement 15 The system must be able to capture laboratory testing and results for person records. Data The system must be able to capture laboratory Components information, including but not limited to laboratory name, specimen ID, specimen type, collection date, ordering provider, ordering O.1 facility, test name, result, reference ranges, organism, result date, and serotype. Data The system must for end-users to enter Components multiple lab tests and results for each person O.2 and each reportable condition. Functional Requirement 16 The system must capture needed disease-specific data fields. Data The system must be able to capture clinical and Components epidemiologic data including but not limited to P.1 dates, treatments, hospitalization, and symptoms. Data The system must be able to capture drug Components susceptibilities for relevant reportable P.2 conditions. Data The system must be able to capture travel Components history, including type of travel, dates of travel, P.3 departures, and destinations. Data The system must allow for food history Components questions, including but not limited to food and water consumption, food handling, stores where P.4 food was purchased, restaurants or other locations where food was consumed, travel and other exposures. The system must be able to track vaccination Data Components history of cases, including vaccination date, vaccination time, vaccine type, manufacturer, lot P.5 number, administering facility, and reason not vaccinated. Please see pp. 76-77 of
N.2 Data Components The system must allow for multiple field entries for fields, including but not limited to address, phone number, guardian and race. Functional Requirement 15 The system must be able to capture laboratory testing and results for person records. O.1 Data Components The system must be able to capture laboratory information, including but not limited to laboratory name, specimen ID, specimen type, collection date, ordering provider, ordering facility, test name, result, reference ranges, organism, result date, and serotype. O.2 Data Components The system must for end-users to enter multiple lab tests and results for each person and each reportable condition. Functional Requirement 16 The system must capture needed disease-specific data fields. P.1 Data Components The system must be able to capture clinical and epidemiologic data including but not limited to dates, treatments, hospitalization, and symptoms. P.2 Data Components The system must be able to capture drug susceptibilities for relevant reportable conditions. P.3 Data Components The system must be able to capture travel history, including type of travel, dates of travel, departures, and destinations. P.4 Data Components The system must allow for food history questions, including but not limited to food and water consumption, food handling, stores where food was purchased, restaurants or other locations where food was consumed, travel and other exposures. P.5 Data Components The system must be able to track vaccination history of cases, including vaccination date, vaccination time, vaccine type, manufacturer, lot number, administering facility, and reason not vaccinated. Please see pp. 76-77 of