Allow a person to take a test through BFT portal

[AlbertoDePena]

Create a web portal for gathering required parameters to generate a link to allow a person to take a test.

1. Create a landing web page
2. Gather require info to request test link from CNSVS
3. Post user info to CNSVS endpoint to request test link
4. Embed (iframe) CNSVS testing portal
5. Within same web portal, check to see if CNSVS test result has been posted to our endpoint
6. Display message explaining any invalid tests and provide a new test link containing only the needed tests to retake
7. Once the test has been completed successfully, generate test report (see test report PDF) and allow the user to print

[AlbertoDePena]

Dev Stack

Azure free trial is over... might have to consider using something like DigitalOcean (cheaper)

• Docker
• Linux Ubuntu
• F#, Giraffe, RabbitMQ, Meisois, Postgres DB
• Azure Durable Functions - could be best option since no need to manage hosting resources

API Gateway

• Single entry point (C# - Refit)

Web Portal

• Client web app for test taking workflow

Patient API

• GET - search patients based on some criteria
• GET - get single patient by ID
• GET - get test results for a given patient
• POST - create new patient
• POST - insert new test result for a given patient (endpoint used by CNSVS provider)
• PATCH - update patient

Report API

• GET - get report data for a completed test for a given patient. This would be metadata to generate (HTML) report on the client app. This would allow the patient to print/share the report

Report Service

• Subscribe to test results from CNSVS provider. Parse test results and denormalize to facilitate report generation

[AlbertoDePena]

Azure Durable Function Design

• Web client - meisosis or aurelia app hosted in Azure Storage (blob)
• Orchestratror - HTTP trigger for posting tests results
• Activity - store test results
• Activity - normalize test results
• Activity - generate report data
• Activity - store report data / tester info in Cosmos DB
• API - HTTP trigger for getting test results / tester info
• API - HTTP trigger for posting tester main info

[AlbertoDePena]

Possible schema if using Azure Cosmos DB

• Tester schema

{
        "id": "",
    "firstName": "",
    "lastName": "",
    "email": "",
        "dob": "",
    "testResults": [
        {
            "cnsvs_id": "",
            "account_id": "",
            "test_date": "",
            "test_time": "",
            "timezone": "",
            "gmt_test_date": "",
            "gmt_test_time": "",
            "subject_id": "",
            "birth_date": "",
            "gender": "",
            "duration": "",
            "language": "",
                        "domain_data": "",
            "report_data": ""
        }
    ]
}

[AlbertoDePena]

Clean up

• Do not use task in internal code, only from orchestrator / activity function
• Include Async bind / map / return to do function composition

[AlbertoDePena]

New requirements

• Subject ID can be generated - make sure to look at format criteria (documentation)
• Email is required and must be unique
• Test report can be generated as HTML page. Provide a way to print as PDF
• Do not present sensitive info in the client: BFT username/password and account ID

[AlbertoDePena]

New Requirements as of May 16 (deliverable on Monday 20)

• Make a test-config main/landing page
• Remove scheduling option
• Expect first/last name, email, and test_config as param (new account)
• Expect email and test_config as param
• Email, first/last name is readonly
• DOB is required
• If has test results, show complete page (Chris to provide mockup)
• If no test results, show page to generate a new link (Chris to provide mockup)