From e03636304cade2446798f593a6a7492fc70ff5d4 Mon Sep 17 00:00:00 2001 From: Andy Walker Date: Wed, 14 Aug 2024 15:33:58 -0700 Subject: [PATCH 1/6] Create medicare-cardholders - Adding new page for Medicare cardholders use case --- docs/enrollment-pathways/medicare-cardholders | 1 + 1 file changed, 1 insertion(+) create mode 100644 docs/enrollment-pathways/medicare-cardholders diff --git a/docs/enrollment-pathways/medicare-cardholders b/docs/enrollment-pathways/medicare-cardholders new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/docs/enrollment-pathways/medicare-cardholders @@ -0,0 +1 @@ + From 4f298a640050408c8376776d4de3e4592f035d6f Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Wed, 14 Aug 2024 22:34:21 +0000 Subject: [PATCH 2/6] chore(pre-commit): autofix run --- docs/enrollment-pathways/medicare-cardholders | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/enrollment-pathways/medicare-cardholders b/docs/enrollment-pathways/medicare-cardholders index 8b1378917..e69de29bb 100644 --- a/docs/enrollment-pathways/medicare-cardholders +++ b/docs/enrollment-pathways/medicare-cardholders @@ -1 +0,0 @@ - From e9fc853e13c5e47e104024ce178221ed7980b186 Mon Sep 17 00:00:00 2001 From: Andy Walker Date: Wed, 14 Aug 2024 17:29:18 -0700 Subject: [PATCH 3/6] Update and rename medicare-cardholders to medicare-cardholders.md - added the .md extension to the filename (face palm) - added Mermaid diagram - added use case content --- docs/enrollment-pathways/medicare-cardholders | 0 .../medicare-cardholders.md | 101 ++++++++++++++++++ 2 files changed, 101 insertions(+) delete mode 100644 docs/enrollment-pathways/medicare-cardholders create mode 100644 docs/enrollment-pathways/medicare-cardholders.md diff --git a/docs/enrollment-pathways/medicare-cardholders b/docs/enrollment-pathways/medicare-cardholders deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/enrollment-pathways/medicare-cardholders.md b/docs/enrollment-pathways/medicare-cardholders.md new file mode 100644 index 000000000..dac741cba --- /dev/null +++ b/docs/enrollment-pathways/medicare-cardholders.md @@ -0,0 +1,101 @@ +# Medicare cardholders use case + +## Overview + +This use case describes a feature in the [Cal-ITP Benefits app](https://benefits.calitp.org) that allows Californians to verify their active participation in the Medicare program to receive reduced fares for transit when paying by contactless debit or credit card at participating transit operators in California. + +**Actor:** A person who uses public transit in California. For benefit eligibility, a Medicare cardholder is a person who has enrolled in the Medicare program, has a Medicare.gov account, and is not deceased. + +**Goal:** To verify a transit rider’s Medicare status so they receive reduced fares when paying by contactless debit or credit card. + +**Precondition:** The California transit operator offers fixed route service, has installed and tested validator hardware necessary to collect fares using contactless payment on bus or rail lines, and the operator has a policy in place to offer a transit discount to riders enrolled in Medicare. +## Basic Flow + +```mermaid +sequenceDiagram +autonumber +%% Medicare Cardholders Enrollment Pathway + actor Transit Rider + participant Benefits as Benefits app + participant IdG as Identity Gateway + participant Medicare as Medicare.gov + participant BB API as Blue Button API + participant Littlepay +Transit Rider->>Benefits: visits benefits.calitp.org + activate Benefits +Benefits-->>IdG: begin eligibility verification + activate IdG +Transit Rider->>Medicare: account authentication + activate Medicare +Medicare->>IdG: authentication confirmation + deactivate Medicare +IdG-->>BB API: requests required PII + activate BB API +BB API-->>IdG: returns required PII + deactivate BB API +IdG-->>Benefits: eligibility response + deactivate IdG +Benefits-->>Littlepay: card enrollment start + activate Littlepay +Transit Rider->>Littlepay: provides debit or credit card details +Littlepay-->>Benefits: card enrollment confirmation + deactivate Littlepay + deactivate Benefits +``` + +1. The transit rider visits the web application at benefits.calitp.org in a browser on their desktop computer. + +1. The transit rider chooses the transit operator that serves an area where they want to ride public transit. + +1. The transit rider chooses to verify their eligibility as a person who is living and enrolled in Medicare. + +1. The transit rider authenticates with their existing Medicare.gov account or, if they don’t have one, creates a Medicare.gov account using their Medicare card. + +1. The Cal-ITP Benefits app interfaces with the [California Department of Technology Identity Gateway](https://digitalidstrategy.cdt.ca.gov/primary-elements.html) (IdG) to verify benefit eligibility. The IdG uses successful authentication with Medicare.gov and personal information shared by the Blue Button API to verify Medicare status. + +1. The IdG uses the response provided by Blue Button API to determine the rider’s eligibility for a transit benefit. + +1. The IdG then passes an eligibility response as Medicare enrollment status = TRUE to the Cal-ITP Benefits app to indicate the person is eligible for a benefit. + +1. The transit rider provides the debit or credit card details they use to pay for transit to Littlepay, the payment processor that facilitates transit fare collection. + +1. The app registers the transit benefit with the transit rider’s debit or credit card. + +## Alternative Flows + +- Suppose the transit rider does not have a desktop computer. In this case, they open the web application at benefits.calitp.org in a mobile browser on their iOS or Android tablet or mobile device to complete enrollment using the basic flow. + +- Suppose the transit rider cannot authenticate with Medicare.gov, or will not create an account. In either case, the app cannot determine their Medicare status and they cannot enroll their contactless debit or credit card for a reduced fare. + +- Suppose the CDT Identity Gateway returns Medicare enrollment status = FALSE. In that case, the Cal-ITP Benefits app will not allow the transit rider to enroll their contactless debit or credit card for a reduced fare. + +- Suppose the debit or credit card expires or is canceled by the issuer. In that case, the transit rider must repeat the basic flow to register the new debit or credit card. + +- If the transit rider uses more than one debit or credit card to pay for transit, they repeat the basic flow for each card. + +## Postcondition + +The transit rider receives a fare reduction each time they use the debit or credit card they registered to pay for transit rides. The number of times they can use the card to pay for transit is unlimited and the benefit never expires. + +## Benefits + +- The transit rider no longer needs cash to pay for transit rides. + +- The transit rider doesn’t have to lock up funds on a closed-loop card offered by the transit operator. + +- The transit rider pays for transit rides with their debit or credit card, just as they do for groceries, a cup of coffee, or any other good or service. + +- The transit rider can enroll in a transit benefit from home when convenient; they do not have to visit a transit agency in person. + +- Secure state and federal solutions manage the transit rider’s personal identifiable information (PII): Medicare.gov, the Blue Button API, and the California Department of Technology Identity Gateway (IdG). Transit riders do not have to share personal information with local transit operators. + +- Benefit enrollment takes minutes rather than days or weeks. + +- Benefit enrollment doesn’t require online accounts with private companies. + +## Example Scenario + +A 46-year old person with End-Stage Renal Disease (ESRD) uses public transit to get to and from dialysis treatments. They have undergone dialysis treatments for the last four months and are now covered by Medicare. In order to save on transportation expenses, they scheduled an appointment with their local transit agency and made a special trip to complete the in-person eligibility process to qualify for reduced transit fares. They now receive a 50% fare reduction but have to pay for transit rides using the closed-loop card provided by the operator to receive the reduced fare. It’s frustrating and inconvenient to reload this closed-loop agency card in $10 payments every week, especially because they sometimes could use the money tied up on the card to make ends meet. In summary, this person pays for daily expenses using several forms of payment: their agency card for transportation and their debit card or cash for everything else. + +The transit operator serving their region of California implements contactless payments on fixed bus routes throughout the service area. This rider opens the Cal-ITP Benefits web application at home, completes the workflow to digitally confirm they are enrolled in Medicare, and registers their debit card for reduced fares. Now, when they tap-to-pay when boarding the bus, they are automatically charged the reduced fare. They no longer need to use their closed-loop agency card to pay for transit and have complete access to all funds in their weekly budget. + From 29a4cb1b840d8d46c44640e174ba1b951abb5063 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu, 15 Aug 2024 00:29:29 +0000 Subject: [PATCH 4/6] chore(pre-commit): autofix run --- docs/enrollment-pathways/medicare-cardholders.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/enrollment-pathways/medicare-cardholders.md b/docs/enrollment-pathways/medicare-cardholders.md index dac741cba..c27b0da71 100644 --- a/docs/enrollment-pathways/medicare-cardholders.md +++ b/docs/enrollment-pathways/medicare-cardholders.md @@ -32,7 +32,7 @@ Medicare->>IdG: authentication confirmation IdG-->>BB API: requests required PII activate BB API BB API-->>IdG: returns required PII - deactivate BB API + deactivate BB API IdG-->>Benefits: eligibility response deactivate IdG Benefits-->>Littlepay: card enrollment start @@ -95,7 +95,6 @@ The transit rider receives a fare reduction each time they use the debit or cred ## Example Scenario -A 46-year old person with End-Stage Renal Disease (ESRD) uses public transit to get to and from dialysis treatments. They have undergone dialysis treatments for the last four months and are now covered by Medicare. In order to save on transportation expenses, they scheduled an appointment with their local transit agency and made a special trip to complete the in-person eligibility process to qualify for reduced transit fares. They now receive a 50% fare reduction but have to pay for transit rides using the closed-loop card provided by the operator to receive the reduced fare. It’s frustrating and inconvenient to reload this closed-loop agency card in $10 payments every week, especially because they sometimes could use the money tied up on the card to make ends meet. In summary, this person pays for daily expenses using several forms of payment: their agency card for transportation and their debit card or cash for everything else. +A 46-year old person with End-Stage Renal Disease (ESRD) uses public transit to get to and from dialysis treatments. They have undergone dialysis treatments for the last four months and are now covered by Medicare. In order to save on transportation expenses, they scheduled an appointment with their local transit agency and made a special trip to complete the in-person eligibility process to qualify for reduced transit fares. They now receive a 50% fare reduction but have to pay for transit rides using the closed-loop card provided by the operator to receive the reduced fare. It’s frustrating and inconvenient to reload this closed-loop agency card in $10 payments every week, especially because they sometimes could use the money tied up on the card to make ends meet. In summary, this person pays for daily expenses using several forms of payment: their agency card for transportation and their debit card or cash for everything else. The transit operator serving their region of California implements contactless payments on fixed bus routes throughout the service area. This rider opens the Cal-ITP Benefits web application at home, completes the workflow to digitally confirm they are enrolled in Medicare, and registers their debit card for reduced fares. Now, when they tap-to-pay when boarding the bus, they are automatically charged the reduced fare. They no longer need to use their closed-loop agency card to pay for transit and have complete access to all funds in their weekly budget. - From 0f261d4a57397e13d864d24f12440eaf7671b5dd Mon Sep 17 00:00:00 2001 From: Andy Walker Date: Thu, 15 Aug 2024 10:53:28 -0700 Subject: [PATCH 5/6] Add link to Blue Button API site Co-authored-by: machiko --- docs/enrollment-pathways/medicare-cardholders.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/enrollment-pathways/medicare-cardholders.md b/docs/enrollment-pathways/medicare-cardholders.md index c27b0da71..5716e33b7 100644 --- a/docs/enrollment-pathways/medicare-cardholders.md +++ b/docs/enrollment-pathways/medicare-cardholders.md @@ -51,7 +51,7 @@ Littlepay-->>Benefits: card enrollment confirmation 1. The transit rider authenticates with their existing Medicare.gov account or, if they don’t have one, creates a Medicare.gov account using their Medicare card. -1. The Cal-ITP Benefits app interfaces with the [California Department of Technology Identity Gateway](https://digitalidstrategy.cdt.ca.gov/primary-elements.html) (IdG) to verify benefit eligibility. The IdG uses successful authentication with Medicare.gov and personal information shared by the Blue Button API to verify Medicare status. +1. The Cal-ITP Benefits app interfaces with the [California Department of Technology Identity Gateway](https://digitalidstrategy.cdt.ca.gov/primary-elements.html) (IdG) to verify benefit eligibility. The IdG uses successful authentication with Medicare.gov and personal information shared by the [Blue Button API](https://bluebutton.cms.gov/) to verify Medicare status. 1. The IdG uses the response provided by Blue Button API to determine the rider’s eligibility for a transit benefit. From 66b9c7b15c629f53a995f7338f893d29cdef4c34 Mon Sep 17 00:00:00 2001 From: Andy Walker Date: Thu, 15 Aug 2024 11:02:45 -0700 Subject: [PATCH 6/6] Changed doc title - removed "use case" suffix so title aligns with other use cases --- docs/enrollment-pathways/medicare-cardholders.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/enrollment-pathways/medicare-cardholders.md b/docs/enrollment-pathways/medicare-cardholders.md index 5716e33b7..48e8c3c6c 100644 --- a/docs/enrollment-pathways/medicare-cardholders.md +++ b/docs/enrollment-pathways/medicare-cardholders.md @@ -1,4 +1,4 @@ -# Medicare cardholders use case +# Medicare cardholders ## Overview