Ball Park Ticket Taker - Revision history

Tom: /* References */

2025-08-10T00:51:22Z

‎References

Tom: /* Issues */

2021-12-08T06:10:57Z

‎Issues

Tom: /* Scenarios */

2021-11-23T22:21:59Z

‎Scenarios

Tom: /* Scenarios */

2021-11-23T22:20:48Z

‎Scenarios

Tom: /* References */

2021-11-23T22:02:25Z

‎References

Tom: /* References */

2021-11-23T22:01:38Z

‎References

Tom: /* Unsuccessful Outcome */

2021-11-23T22:00:58Z

‎Unsuccessful Outcome

Tom at 19:00, 23 November 2021

2021-11-23T19:00:17Z

Tom: /* Successful Outcome */

2021-11-23T17:40:33Z

‎Successful Outcome

Tom: /* Successful Outcome */

2021-11-23T17:29:58Z

‎Successful Outcome

← Older revision		Revision as of 00:51, 10 August 2025
Line 73:		Line 73:
	[[Category: Profile]]		[[Category: Profile]]
	[[Category: Use Case]]		[[Category: Use Case]]
		+	[[Category: Physical Access]]

@@ Line 57: / Line 57: @@
 ==Issues==
-# The patron is one of the 19% of the population w/o a smart phone. Perhaps her grandchild can help with that.
+# If the patron is one of the 19% of the population w/o a smart phone, perhaps her grandchild can help with that.
-# Getting the wallet into the patron's smart phone or lap top may prove to be challenging.
+# Getting the wallet into the patron's smart phone or laptop may prove to be challenging.
 # The patron is not comfortable with technology.
 # Who determines what data from the MDL is sent to ticket-master, or the ball part?  (e.g., the public health details or explicit user consent)?

@@ Line 35: / Line 35: @@
 # One cleared for entry the patron may need to present the token again to access the private box floor. If alcoholic beverages are served in the box, some addition scans may be required to acquire them.
 # During the game or at half time, the patron may walk to other areas that have age or other restrictions.
-# To return to the box level a scan or visual viewing may be required again. This process can be automated if the gate to the box level is automated. That gate may also have facial recognition.
+# To return to the box level a scan or visual viewing may be required again.
 ===Alternate Scenario===
 # Radio media can be enabled from the smartphone. This is typically by use of [[BLE]] or [[NFC]] radios.
 ==Successful Outcome==

@@ Line 28: / Line 28: @@
 ==Scenarios==
-Primary Scenario:
+===Primary Scenario===
-# Person desires to attend a ball game in one of the private boxes. The process of [[Ball Park Ticket Acquisition]] is described in that use case.
+# A patron desires to attend a ball game in one of the private boxes and acquires a ticket that is combined with all related attributes to successfully attend the ball game. The process of [[Ball Park Ticket Acquisition]] is describes that use case.
 ==Successful Outcome==

← Older revision		Revision as of 22:02, 23 November 2021
Line 62:		Line 62:

	[[Category: Profile]]		[[Category: Profile]]
−	[[Category: Use ~~Cases~~]]	+	[[Category: Use Case]]

@@ Line 56: / Line 56: @@
 ==References==
-This use case was updated on 2021-11-11.
+This use case was updated on 2021-11-22.
 * See [[Mobile Driver's License]] in this wiki.

@@ Line 37: / Line 37: @@
 ==Unsuccessful Outcome==
-# Validity of the access token is tested by the patron before travel to the park. This is a better outcome that getting to the park and then being denied access, so it should be considered a partial success.
+# Validity of the access token is tested by the patron before travel to the park. This is a better outcome that getting to the park and then being denied access, so it should be considered a partial success. This also covers the case where the local health agency has changed the rules for access to the ball park after the patron acquired the access token. While the preferred path is for the ticker seller to notify the user, the ability of the user to validate access allows them time to adapt to any post-sale changes.
 #Failure to access at main gate. The reason should be clear as a ticket counter available to get adjustments as required.
 ==Privacy Concerns==

@@ Line 1: / Line 1: @@
 ==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.
+This use case considers a user trying to attend a ball game at a park that requires full COVID immunizations as defined by the local health agency.
 ==Context==
@@ Line 51: / Line 51: @@
 # Getting the wallet into the patron's smart phone or lap top may prove to be challenging.
 # The patron is not comfortable with technology.
-# Who determines what data from the MDL is sent to ticket-master, or the ball part?  (e.g., the public health deyails or explicit user consent)?
+# Who determines what data from the MDL is sent to ticket-master, or the ball part?  (e.g., the public health details or explicit user consent)?
 # Is the driver's license ID number may be used for long term tracking of the user.?
 # Is a picture required for patron matching to the person at the access points.
@@ Line 59: / Line 59: @@
 This use case was updated on 2021-11-11.
-* [[Mobile Driver's License]] in this wiki.
+* See [[Mobile Driver's License]] in this wiki.
-[[Category:Profile]]
+[[Category: Profile]]
-[[Category:Use Cases]]
+[[Category: Use Cases]]

@@ Line 10: / Line 10: @@
 ===Actors===
-#Actor: Person seeking access to one game
+#Actor: Patron seeking access to one (or more) game.
-#Actor: Proxy is used here to mean any person that can hold an access token for another.
+#Actor: Proxy is used here to mean any person that can hold an access token for another, typically a child.
-#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.
+#Actor: Validation web site that can analyze a person's access token remotely to let them know what access would be granted if used at the ballpark.
 #Actor: Ballpark intake personnel both at the main entrance and at the access point to the private boxes.
@@ Line 37: / Line 37: @@
 ==Unsuccessful Outcome==
-# Not all of the patron's records are available in a single wallet and some action in the real-world is required to get them altogether.
+# Validity of the access token is tested by the patron before travel to the park. This is a better outcome that getting to the park and then being denied access, so it should be considered a partial success.
-# The
+#Failure to access at main gate. The reason should be clear as a ticket counter available to get adjustments as required.
-# The ticket holder feels that the ease of access was not sufficient to meet their needs.
 ==Privacy Concerns==
 * The access token may contain more information that is required for the current visit.
-* The
+* Presence or lack of specific attributes in the token can be determine at any access point in the park.
 ==Issues==
-# The patient is one of the 19% of the population w/o a smart phone. Perhaps her grandchild can help with that.
+# The patron is one of the 19% of the population w/o a smart phone. Perhaps her grandchild can help with that.
-# Getting the wallet into the patient's smart phone or lap top may prove to be challenging.
+# Getting the wallet into the patron's smart phone or lap top may prove to be challenging.
-# The patient is not comfortable with technology.
+# The patron is not comfortable with technology.
-# Who determines what data from the MDL is sent to the EHR?  (e.g., the healthcare community specs or explicit user consent)?
+# Who determines what data from the MDL is sent to ticket-master, or the ball part?  (e.g., the public health deyails or explicit user consent)?
-# Is the driver's license ID number included in any way?
+# Is the driver's license ID number may be used for long term tracking of the user.?
-# Is a picture required for patient record matching to the person on the telemedicine call.
+# Is a picture required for patron matching to the person at the access points.
 # Is fraud one of the threats to be addressed within the scope of the recommendation?
@@ Line 57: / Line 59: @@
 This use case was updated on 2021-11-11.
-* [[Mobile Driver's License]] on IDESG wiki.
+* [[Mobile Driver's License]] in this wiki.
 [[Category:Profile]]
 [[Category:Use Cases]]

@@ Line 32: / Line 32: @@
 ==Successful Outcome==
-# The patient is correctly matched to their electronic health record.
+# The patron is able to present a access token at the main entrance and get through the metal detector with low hassle.
-# The patient has a successful telemedicine experience, receives a set of reports, is schedules for a lab test and immunization at the local pharmacy.
+# Access checks at internal points can all be enabled with the same access token used at the main entrance.
-# Follow up procedures are created and sent to her smartphone and give her notices when she must take medicine or other procedures.
+# Where access is denied the patron can be informed of the required attribute that was not available in the token.
 ==Unsuccessful Outcome==