Mobile Application Guidance

Mobile application reference workflow

A suggested mobile application workflow is shown below. App developers have flexibility to modify the flow as appropriate to ensure (1) transparency in how data will be managed, (2) user has control over data, and (3) ease of use in taking the test and reporting results.

Image
Mobile application guidance

Digital testing applications should attempt to collect the following information from the user. This information should then be encoded in the test result message and sent to the hub:

FieldData Entry FormatUser Requirement
(app requests all fields)
AgeNumeric; Populate based on date of birth if availableUser entry required
Zip codeNumericUser entry required
Date of testDateUser entry required
SexFemale | Male | OtherUser entry optional
RaceAmerican Indian or Alaska Native | Asian | Black or African American | Native Hawaiian or Other Pacific Islander | White | OtherUser entry optional
EthnicityHispanic or Latino | Not Hispanic or LatinoUser entry optional
Are you symptomatic?Yes | No | UnknownUser entry optional
Date of symptom onsetDateRequired to ask if 'Are you symptomatic' is 'Yes'; User entry optional.
First name*TextUser entry optional
Middle name*TextUser entry optional
Last name*TextUser entry optional
Date of birth*DateUser entry optional
Street address*TextUser entry optional
City*TextUser entry optional
StatePopulate based on zip codeUser entry optional
CountyText; Select from list based on zip codeUser entry optional
Phone number*NumericUser entry optional
Email address*TextUser entry optional

* The hub will remove these PII fields from the test result message before forwarding it to the federal health system HHS Protect .