Abstract: An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities and healthcare providers that can act as data, service, product and service providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR data blockchain system can provide workflow on the blockchain that can utilize smart contracts to define workflow processes, expected outcomes, and financial costs. When a prescription transaction is complete, it will result in the settlement of each of the smart contracts that were added to the prescription workflow.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: A card reader for use with a mobile device includes a foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A card reader for use with a mobile device includes a foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A card reader for use with a mobile device includes a foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A system and method for a frame-based internet enabled interface. In one embodiment, a system is disclosed for a client-side frame based internet enabled interface. The system comprises a first frame and a second frame in a window. The first frame encapsulates a resource from a third-party internet based service. The resource is requested by a user through an internet enabling software. In addition, the second frame comprises user-specific information that is related to content provided from the resource.

Abstract: One or more Bluetooth® low energy (BLE) beacons in communication with a remote server that provides check in capabilities and payment capabilities may be installed at a location. The BLE beacons may connect with a user's mobile device when the user enters the location and allow the user to check in to the location and authorize payments to be made at the location. Once the user is checked in to the location, the user may be provided with additional functionality, benefits, offers, and applications related to the location and facilitated by the check in. Further, the user may be pre-checked in into a next location when the user is at a current location.

Abstract: A user makes a purchase request through a merchant app on a mobile device, such as by selecting an item for purchase. A mobile SDK of a payment provider is installed in the merchant app. The payment request includes the phone number for the mobile device. The payment provider verifies the phone number of the user and requests approval of the payment from a mobile operator providing wireless communication services on the mobile device. If the request is approved, the payment is charged to the user mobile operator account. The user simply taps a button to select an item to purchase and selects another button to confirm the purchase. Once processing is done, the user is notified on the mobile device of a successful payment.

Abstract: A card reader for use with a mobile device includes a foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A user makes a purchase request through a merchant app on a mobile device, such as by selecting an item for purchase. A mobile SDK of a payment provider is installed in the merchant app. The payment request includes the phone number for the mobile device. The payment provider verifies the phone number of the user and requests approval of the payment from a mobile operator providing wireless communication services on the mobile device. If the request is approved, the payment is charged to the user mobile operator account. The user simply taps a button to select an item to purchase and selects another button to confirm the purchase. Once processing is done, the user is notified on the mobile device of a successful payment.

Abstract: A card reader for use with a mobile device includes a rotatable face that can be rotated over a portion of the mobile device so that when the user slides a card through the card reader, the overlapping portion of the rotatable face prevents the card reader from spinning or rotating. A foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A card reader for use with a mobile device includes a rotatable face that can be rotated over a portion of the mobile device so that when the user slides a card through the card reader, the overlapping portion of the rotatable face prevents the card reader from spinning or rotating. A foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.

Abstract: A card reader for use with a mobile device includes a rotatable face that can be rotated over a portion of the mobile device so that when the user slides a card through the card reader, the overlapping portion of the rotatable face prevents the card reader from spinning or rotating. A foot and/or a housing for a jack on the bottom of the card reader prevents the card reader from accidently turning off the mobile device during use.