Difference between revisions of "Ball Park Ticket Taker"

Revision as of 04:29, 23 November 2021

Full Title

This use case considers a user trying to attend a ball game at a park that requires full COVID immuniations as defined by the local health agency.

Context

• This use case considers the primary user to be the Ticket Taker. A companion use case will consider the attendee in Ball Park Ticket Acquisition.
• While it would be interesting to just consider the purchaser going to general admission, this use case will include access to one of the boxes that serves alcoholic beverages and requires proof of age as well. While not all of the conditions are required, the complex case is helpful to determine the widest range of in order to anticipate some of the complexity that may be needed in the future.

Goal

To enable the creation of a single aggregated claim set for authorizing access to a ballpark's main entrance asl well as to areas within the park like the level with private boxes. 's

Actors

1. Actor: Person seeking access to one game
2. Actor: Proxy is used here to mean any person that can hold an access token for another.

Actor: Validation web site that can analyze a person's access token remotely to le them know what access would be granted if used at the ballpark.

1. Actor: Ballpark intake personnel both at the main entrance and at the access point to the private boxes.

Preconditions

• The patient is in need of healthcare using telemedicine and is not currently known to the practice.
• The patient has access to a mobile device that can authenticate the user and communicate to the physician or pratice.

Trigger

The person arriving at the access point with a cell phone containing the access token.

Scenarios

Primary Scenario:

1. Patient receives notice of appointment and instructions for online registration, or in person if she wants to risk it.
2. Patient has a mobile driver's license (MDL) and doesn't want to travel to the doctor's office, which is why she chose telemedicine in the first place.
3. Patient has an insurance card that is machine readable.
4. Patient has a mobile wallet that holds the MDL and can take a picture of the insurance card.
5. Patient navigates to the telemedicine web site which can send a message to her wallet to provide the mdl and insurance card as an image.
6. Her wallet understands that an image of some sort is required and helps with the image capture.
7. The data required from the MDL, the image capture and potential other data is presented to the user as a consent screen.
8. The patient chooses to send the data to the telemedicine web site.
9. The visit with the physician can start immediately, or when the physician becomes available.

Bonus capability.

1. The patient is asked for prior health history and is able to navigate to her PCP and get a QR code that can be included in the message to the telemedicine site which can get the history data.
2. The patient has a wallet that can authenticate the user's presence and allows the user to enter their existing driver's card as a machine-readable image.

Secondary Scenario:

1. Patient schedules a lab visit after the telemedicine session is completed.

Tertiary Scenario:

1. The patient's grandchild acts on her behalf as an access proxy.

Successful Outcome

1. The patient is correctly matched to their electronic health record.
2. The patient has a successful telemedicine experience, receives a set of reports, is schedules for a lab test and immunization at the local pharmacy.
3. Follow up procedures are created and sent to her smartphone and give her notices when she must take medicine or other procedures.

Unsuccessful Outcome

1. Not all of the patient's records are available on-line and some action in the real-world is required to get them altogether.
2. The Telemedical connection fails or is not of sufficient quality for the physician to complete the examination.
3. The patient feels that the quality of care was not sufficient to meet their needs.

Privacy Concerns

• The EHR may release more information that is required for the current visit.
• The patient may be in close quarters with others that should not hear the results of the session.

Issues

1. The patient is one of the 19% of the population w/o a smart phone. Perhaps her grandchild can help with that.
2. Getting the wallet into the patient's smart phone or lap top may prove to be challenging.
3. The patient is not comfortable with technology.
4. Who determines what data from the MDL is sent to the EHR? (e.g., the healthcare community specs or explicit user consent)?
5. Is the driver's license ID number included in any way?
6. Is a picture required for patient record matching to the person on the telemedicine call.
7. Is fraud one of the threats to be addressed within the scope of the recommendation?

References

This use case was updated on 2021-11-11.

• Mobile Driver's License on IDESG wiki.