US20180144096A9 - Connected Medical Devices - Google Patents
Connected Medical Devices Download PDFInfo
- Publication number
- US20180144096A9 US20180144096A9 US14/078,440 US201314078440A US2018144096A9 US 20180144096 A9 US20180144096 A9 US 20180144096A9 US 201314078440 A US201314078440 A US 201314078440A US 2018144096 A9 US2018144096 A9 US 2018144096A9
- Authority
- US
- United States
- Prior art keywords
- secure element
- medical
- mobile device
- information
- nfc
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000006854 communication Effects 0.000 claims description 40
- 238000004891 communication Methods 0.000 claims description 40
- 238000000034 method Methods 0.000 claims description 31
- 238000012545 processing Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 6
- 230000005055 memory storage Effects 0.000 claims 4
- 230000036541 health Effects 0.000 abstract description 43
- 239000008280 blood Substances 0.000 abstract description 6
- 210000004369 blood Anatomy 0.000 abstract description 6
- 238000002649 immunization Methods 0.000 abstract description 4
- 230000003053 immunization Effects 0.000 abstract description 4
- 210000000056 organ Anatomy 0.000 abstract description 4
- WQZGKKKJIJFFOK-GASJEMHNSA-N Glucose Natural products OC[C@H]1OC(O)[C@H](O)[C@@H](O)[C@@H]1O WQZGKKKJIJFFOK-GASJEMHNSA-N 0.000 abstract description 3
- 230000036772 blood pressure Effects 0.000 abstract description 3
- 239000008103 glucose Substances 0.000 abstract description 3
- 238000010295 mobile communication Methods 0.000 description 43
- 238000012546 transfer Methods 0.000 description 22
- 238000007726 management method Methods 0.000 description 17
- 230000007175 bidirectional communication Effects 0.000 description 16
- 206010020751 Hypersensitivity Diseases 0.000 description 7
- 230000007815 allergy Effects 0.000 description 7
- 230000006698 induction Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 229940079593 drug Drugs 0.000 description 3
- 239000003814 drug Substances 0.000 description 3
- 238000003780 insertion Methods 0.000 description 3
- 230000037431 insertion Effects 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- HVYWMOMLDIMFJA-DPAQBDIFSA-N cholesterol Chemical compound C1C=C2C[C@@H](O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H]([C@H](C)CCCC(C)C)[C@@]1(C)CC2 HVYWMOMLDIMFJA-DPAQBDIFSA-N 0.000 description 2
- NOESYZHRGYRDHS-UHFFFAOYSA-N insulin Chemical compound N1C(=O)C(NC(=O)C(CCC(N)=O)NC(=O)C(CCC(O)=O)NC(=O)C(C(C)C)NC(=O)C(NC(=O)CN)C(C)CC)CSSCC(C(NC(CO)C(=O)NC(CC(C)C)C(=O)NC(CC=2C=CC(O)=CC=2)C(=O)NC(CCC(N)=O)C(=O)NC(CC(C)C)C(=O)NC(CCC(O)=O)C(=O)NC(CC(N)=O)C(=O)NC(CC=2C=CC(O)=CC=2)C(=O)NC(CSSCC(NC(=O)C(C(C)C)NC(=O)C(CC(C)C)NC(=O)C(CC=2C=CC(O)=CC=2)NC(=O)C(CC(C)C)NC(=O)C(C)NC(=O)C(CCC(O)=O)NC(=O)C(C(C)C)NC(=O)C(CC(C)C)NC(=O)C(CC=2NC=NC=2)NC(=O)C(CO)NC(=O)CNC2=O)C(=O)NCC(=O)NC(CCC(O)=O)C(=O)NC(CCCNC(N)=N)C(=O)NCC(=O)NC(CC=3C=CC=CC=3)C(=O)NC(CC=3C=CC=CC=3)C(=O)NC(CC=3C=CC(O)=CC=3)C(=O)NC(C(C)O)C(=O)N3C(CCC3)C(=O)NC(CCCCN)C(=O)NC(C)C(O)=O)C(=O)NC(CC(N)=O)C(O)=O)=O)NC(=O)C(C(C)CC)NC(=O)C(CO)NC(=O)C(C(C)O)NC(=O)C1CSSCC2NC(=O)C(CC(C)C)NC(=O)C(NC(=O)C(CCC(N)=O)NC(=O)C(CC(N)=O)NC(=O)C(NC(=O)C(N)CC=1C=CC=CC=1)C(C)C)CC1=CN=CN1 NOESYZHRGYRDHS-UHFFFAOYSA-N 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 208000017667 Chronic Disease Diseases 0.000 description 1
- 206010020772 Hypertension Diseases 0.000 description 1
- 102000004877 Insulin Human genes 0.000 description 1
- 108090001061 Insulin Proteins 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 208000006673 asthma Diseases 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 235000012000 cholesterol Nutrition 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000003168 generic drug Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 229940125396 insulin Drugs 0.000 description 1
- 238000009533 lab test Methods 0.000 description 1
- 238000002483 medication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000002957 persistent organic pollutant Substances 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000036387 respiratory rate Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
- 238000002255 vaccination Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
- G16Z99/00—Subject matter not provided for in other main groups of this subclass
-
- G06F19/323—
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
- G16H10/65—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records stored on portable record carriers, e.g. on smartcards, RFID tags or CD
Definitions
- the present invention relates to data communications and wireless devices.
- Mobile communication devices e.g., cellular phones, personal digital assistants, and the like—are increasingly being used to conduct payment transaction.
- payment transactions can include, for example, purchasing goods and/or services, tickets, bill payments, and transferring funds between bank accounts.
- bigger screens better user input with touch screens increased processing capability, and faster more reliable wireless mobile devices, can be used to manage electronic medical records.
- Medical devices capture and/or store data.
- medical devices don't export data or not very easily. So, the Health Care Provider (HCP) is required to manually write down the sensor/measurement data displayed on the medical device and/or enter it into a computer which is time consuming, prone to error, and costly.
- HCP Health Care Provider
- While some medical devices have the ability to export data to a personal computer using a cable or wirelessly using blue tooth for example, these few devices have special customized interfaces which are costly and limit the patient and health care provider to using those devices which may not be their preferred medical device. In many instances patients and health care providers prefer to use certain medical devices based on their functionality, cost, or accuracy in capturing measurement data particularly for very serious chronic illnesses where accuracy is extremely important.
- This invention describes various ways to capture data from any medical device and transmit it electronically to mobile devices (e.g. cell phones, smart phones, electronic note books), computers, servers, electronic medical records, etc. by using a secure element that serves as a “universal health port”.
- mobile devices e.g. cell phones, smart phones, electronic note books
- computers e.g. cell phones, smart phones, electronic note books
- servers e.g. electronic medical records
- universal health port e.g. cell phones, smart phones, electronic note books
- the system is configured with a mobile device (with client application also referred to as a mobile wallet), a secure element that is associated with the mobile device, NFC Point Of Sale System which is capable of processing financial transactions (including 2-way wireless terminal capable of sending and transmitting), NFC Point-Of-Presence Terminal which is capable of processing non-financial transactions (including 2-way wireless terminal capable of sending and transmitting), an NFC Point-of-Entry Device which is capable of providing access to venues including 2-way wireless terminal capable of sending and transmitting, a management server, a Trusted Service Manager (TSM) and several 3rdParty artifact provider/aggregator.
- TSM Trusted Service Manager
- the NFC POS/POE/POP device will trigger an application residing in the secure element (which is different than an application residing on the mobile communication device) to power on and activate an application residing in the secure element, transfer data or digital artifacts (e.g debit/prepaid/credit card, receipts, tickets, advertisements, coupons, loyalty points, gift cards, vouchers, content (video, image, ringtone, movie), games, documentation, business cards, tickets, hotel key, health care records, security key, automobile key, etc.) from/to the secure element, and the secure element may issue commands and/or respond to commands just to name a few.
- transfer data or digital artifacts e.g debit/prepaid/credit card, receipts, tickets, advertisements, coupons, loyalty points, gift cards, vouchers, content (video, image, ringtone, movie), games, documentation, business cards, tickets, hotel key, health care records, security key, automobile key, etc.
- New Patients If a new patient is visiting a new doctor for a diagnosis and potentially time sensitive, treatment, patients will need to have medical information, allergies, and prescriptions readily available which may take weeks to receive from previous physician.
- Frequent international travelers Frequent travelers need to track their shots and immunizations for travel abroad. If they may have a sudden health care need, they will need to have access to medical information, allergies, and prescriptions readily available for urgent health care.
- This invention enables patients and health care professionals (nurse, doctor, pharmacist, etc) to manage digital medical artifacts medical digital artifacts (e.g. medical ID, basic patient information, patient contact information, emergency contact information, primary care physician information, health insurance information including co-pay and deductibles, prescriptions, office visit summary, appointment cards, Electronic Medical Records (EMR), lab results, blood type, organ/donor status, vital signs, diagnostic data, immunization records, payments and transaction history, pictures, etc) using an NFC enabled mobile device.
- medical digital artifacts e.g. medical ID, basic patient information, patient contact information, emergency contact information, primary care physician information, health insurance information including co-pay and deductibles, prescriptions, office visit summary, appointment cards, Electronic Medical Records (EMR), lab results, blood type, organ/donor status, vital signs, diagnostic data, immunization records, payments and transaction history, pictures, etc
- EMR Electronic Medical Records
- NFC Point-Of-Presence POP
- POP Point-Of-Entry
- POS Point-Of-Sale
- smart poster smart poster
- POP/POE/POS/etc activates the secure element associated with the NFC enabled mobile device and powers the secure element through induction. So, the secure element need not have its own power source nor does the secure element require use of the battery inside of the mobile device.
- the user may not be able to use the mobile device to place a phone call, receive an SMS, or surf the web, but they will be able to transfer information from their secure element (e.g. medical ID) since the secure element is powered by the remote NFC enabled POP/POS/POE device.
- the secure element can also receive digital artifacts from a POP/POS/POE device such as Xrays, prescriptions, appointment cards, etc even if the battery inside of the mobile communication device lacks power. This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few.
- FIG. 1 illustrates a block diagram of a communication system including a wireless mobile communication device and a management server in accordance with one implementation.
- FIG. 2 illustrates a block diagram of a mobile communication device in accordance with one implementation.
- FIG. 3 illustrates a block diagram of a secure element in accordance with one implementation.
- FIGS. 2 B 1 , 2 B 2 A, 2 B 2 B illustrate more details regarding certain components illustrated in FIG. 1 .
- FIG. 3 illustrates a secure element embedded in an ID card
- FIG. 4 illustrates a secure element embedded in a wristband
- FIG. 5 illustrates more details regarding certain components of a secure illustrated in FIG. 1 of a secure element that is capable of bi-directional communication with a mobile device and transfer of data to a remote server
- FIG. 6 illustrates multiple secure elements coupled to a mobile communication device
- FIG. 7 illustrates secure element applications
- FIG. 8 illustrates medical devices with an externally affixed secure element
- An NFC enabled device is one that includes a secure element and enables contactless transactions which have been described in more detail in previous patents including U.S. patent application Ser. No. 13/184,246, entitled “Using a mobile device to enable purchase of deals and increase customer loyalty” filed on Jul. 15, 2011, U.S. Provisional Patent Application No. 61/445,667, entitled “Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011 and U.S. Provisional Patent Application No. 61/429,246, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element using Inaudible Sound Waves,” filed Jan. 3, 2011 both of which are a continuation in part of U.S. patent application Ser. No.
- FIG. 1 is a block diagram illustrating a communication system 100 in accordance with some embodiments.
- the communication system 100 includes a hand-held, wireless mobile communication device 110 with an antenna 120 for wireless communication.
- the mobile communication device 110 includes a user interface for entering data.
- a display 124 FIG. 2
- the mobile communication device 110 includes a keypad 125 ( FIG. 2 ) for entering data.
- both the radio element 120 and the secure element 130 are both disposed internally within a body of the mobile device 110 as illustrated in FIG. 1 , although in certain embodiments the secure element 130 can be external to the mobile device 110 as described hereinafter.
- the mobile device 110 contain a slot, which allows for the insertion of a secure element 130 into a slot and thus the physical insertion, mechanical and electrical connection as needed.
- the secure element can be purchased independently of the mobile device 110 .
- the secure element 130 can also be disposed into a slot that only provides for physical insertion and mechanical connection to the body of the mobile device 110 , and can then preferably include a transceiver that allows for the communication with the radio element 130 using a wireless local communication channel.
- the radio element 120 also is illustrated as optionally including another transceiver 129 , such as a Bluetooth or WIFI transceiver, which can transmit and receive signals with an external device and then communicate signals to and from the radio processor 123 .
- This additional communication channel allows for communications between other external devices, such as an external Bluetooth enabled smartcard, and provides an additional communication channel that is useful for certain transactions, as described further herein.
- FIG. 2 B 1 illustrates a preferred embodiment of the secure element 130 associated with the mobile device 110 , the secure element 130 being commonly known as a smart card.
- the secure element 130 has a secure processor 132 , a secure memory 133 and a POS/NFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel.
- the secure processor 132 communicates via the secure element driver 128 with the radio processor 123 , using, as mentioned above, signals described in the Java Card 2.1 Platform API Specification.
- the transaction request signals and the transaction response signals associated with the transaction preferably include identification code associated with the user, as well as information relative to the transaction, such as item, quantity, vendor, as is known.
- the POS transceiver 134 is preferably an NFC device of some type, which uses an NFC modem, although it can also be a Bluetooth, WIFI or other transceiver.
- NFC modem such an NFC modem will typically have a set of registers that can be read/written by the secure processor 132 . These registers are in turn available for reading and writing over the RFID communications channel and serve as a sort of shared memory between the secure processor 123 within the secure element 130 and the RFID reader that is associated with the POS terminal 150 . This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few.
- a radio/Bluetooth/WIFI transceiver 136 which can communicate with other devices, such as a transceiver associated with the radio processor 120 or for other external devices having those communication capabilities, thus allowing for more flexibility.
- FIG. 2 B 2 A shows a modified secure element 130 , in which the radio element 120 does not communicate with the secure element through a secure element driver 128 of some type.
- the secure element 130 may be external to the mobile device 110 and as such is not connected to the radio element through the secure element driver 128 .
- this communication channel can be used to wirelessly obtain direct communications between the radio element 120 and the secure element 130 .
- This implementation allows for certain bidirectional communications with other devices, as well as with the radio element 120 , and as such more functionality and flexibility is achieved. This implementation is particularly useful since it establishes a direct local communication path with the radio element 120 , since there is not communications with the radio element 120 via the path of driver 128 .
- either of the transceivers 129 or 136 are not associated with the respective radio element 120 or secure element 130 , and there is no direct connection between the radio element 120 an the secure element 130 , then a direct communication link between the radio element 120 an the secure element 130 will not exist.
- data from a real-time transaction performed using the secure element 130 cannot be made directly available to the radio processor and the applications stored thereon, which can prevent, for example, certain redundancy checks to occur, such as a ticketing application in which, after the ticket order has been placed, the ticketing application in the memory 126 associated with the radio element 130 can be programmed to provide an alert if the ticket receipt, via the management server 180 , has not been received within a certain period of time.
- Such an alert would not be possible to program directly (although it could be programmed indirectly via the button panel on the phone, though such an implementation requires extra user intervention, which, if possible, one attempts to avoid in transactions such as this.
- FIG. 2 B 2 B shows a modified secure element 130 ′′, in which the secure element does not include a processor that is capable of bidirectional communications, but instead is a passive device 138 ′, such as an RFID sticker or some other tag, that allows for a user identification, such that a transaction that is initiated with the passive device 138 ′ will cause the management server 180 to perform the transaction details.
- the code received from the POS terminal 150 or the POE terminal 190 is transmitted from the POS terminal 150 or the POE terminal 190 to the management server 180 , which then takes over the transaction.
- This passive device 138 ′ with the identification code stored thereon, can thus be associated with a mobile device 110 not otherwise equipped for such communications, and the management server 190 can provide transactional information to the mobile device 110 using available channels on the mobile device (such as audio, sms or other known data transmission methods). While bidirectional communications do not occur with other devices, transactions are possible, because the management server 190 is involved.
- FIG. 2 B 2 C illustrates a secure element that is capable of either two-way communication or one-way communication with a POS/POE device that is not affixed to a mobile device nor electrically coupled to the mobile device. Instead the secure element is affixed to a hospital bracelet.
- FIG. 3 illustrates a secure element that is affixed to a affixed to a plastic medical ID card and
- FIG. 4 illustrates a secure element affixed to a affixed to a hospital bracelet, for example.
- a secure element that is not affixed to a mobile device nor is electrically coupled to a mobile device can be incorporated with a key chain, watch, ring, bracelet worn as jewelry.
- a secure NFC processor 132 a secure memory 133 and a POS/NFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel.
- A/D converter 135 a microphone 137 , a speaker 139 , and a, cable 141 , power harvester, 144 , Long range RF transceiver, 146 , and a SE controller, 148 .
- the Secure Element Controller 148 can either be logical or physical.
- the Secure Element Controller is the parent controller and all of the other logical or physical secure elements.
- the Secure Element Controller can issue read/write commands to all of the other logical or physical secure elements.
- the secure element 130 has a secure processor 132 , a secure memory 133 and a POS or NFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel.
- a secure element 130 is internal to the mobile communication device 110 .
- the secure element 130 is externally attached to the mobile communication device 110 .
- the secure element 130 is adhesively affixed or mechanically secured to the housing of the mobile communication device 110 .
- the secure element 130 is housed within a slot in the mobile communication device 110 .
- the secure element 130 includes an antenna 131 for wireless communication.
- the antenna 131 is shown as extending from the secure element 130 for visual clarity, the antenna 131 may be implemented internally within the secure element 130 . Also, the secure element 130 may include more than one antenna 131 . Communication occurs wirelessly between the secure element 130 and the mobile communication device 110 via respective antennas 120 and 131 , over a direct wireless channel 163 between the mobile communication device 110 and the secure element 130 . Thus, in some embodiments, the channel 163 does not pass through a network.
- the point of sale terminal 150 illustrated in FIG. 1 is conventional, in that it has the capability of electronically reading information from a device equipped to transmit information in a format that it reads.
- the reader (not shown) within the point of sale terminal 150 can be of one or many types. If the point of sale terminal reader (not shown) includes the provision for NFC communications, then simply bringing the secure element 130 with the NFC transceiver will cause initiation of a transaction and the transmission of the identification code associated with the secure element 130 and thus the user.
- various software that is downloaded into the memory 126 of the radio element 120 and the secure memory 132 of the secure element 130 , along with software resident on the management server 180 , will cooperate at a layer that is above the physical layer of the communications, in order for the desired transaction to occur.
- This software is implemented using based upon known knowledge of mobile device 110 internals and application platforms, NFC, smartcard internals and application platforms, payment protocols (e.g. PayPass), and the working/workflow associated with POS and POE terminals, and the transaction and management servers.
- the present invention provides for piggybacking a tunneling protocol on top of the payment protocol, so that the secure elements 130 can communicate with the transaction server 170 and/or the management server 180 , without modification to the POS terminal 150 or the POE terminal 190 .
- this includes software within the secure element 130 that embeds the required information in fields which will not adversely affect the performance of the POS terminal 150 and/or the POE terminal 190 , and also software in transaction server 170 that will extract the piggybacked payload, associate the payload with the management server 180 if needed, and then authenticate, authorize, and execute transfers of transaction information to the management server 180 .
- the piggybacked payload is sent, instead of to the transaction server 170 , to the management server 180 , which can then associate the transaction and notify the transaction server 170 , the POS terminal 150 and/or the POE terminal as needed.
- NFC transactions There are several types of NFC transactions.
- POS Point-Of-Sale
- POE Point-Of-Entry
- POP Point-Of-Presence
- the POS/POE/POP activates or powers the secure element 130 through induction and triggers an application residing in the secure element (which is different than an application residing on the mobile communication device. So, the secure element need not have its own power source nor does the secure element require use of the battery inside of the mobile device.
- the user may not be able to use the mobile device to place a phone call, receive an SMS, or surf the web, but they will be able to purchase item and receive coupons and other digital artifacts using the secure element since the secure element is powered by the remote NFC enabled POS/POE/POP device.
- an application residing in the secure element (which is different than an application residing on the mobile communication device) is launched and the application can transfer digital artifacts to the POS/POE/POP and the POS/POE/POP terminal can transmit digital artifacts to the secure element again even if the battery inside of the mobile communication device lacks power.
- the NFC enabled mobile device is active and it can power any NFC device in passive mode including a POS/POE/POP, smart poster, or another NFC enabled mobile device which will described in more detail further herein.
- a POS may receive payment credentials from the secure element which is processed by the transaction server 170
- the POS may transfer a coupon, receipt, or some other digital artifact to the secure element simultaneously during the induction process from the POS terminal 150 , the transaction server 170 or the management server 180 .
- the user need only hold, “wave” or “tap” their NFC enabled device once near the POS and both the transmission of the ticket to the POP and the receipt of the digital artifact will occur simultaneously so the user will not have to “tap” or “wave” their phone twice. This is accomplished through induction as well.
- the POS device/terminal will activate the secure element and an application residing in the secure element (which is different than an application residing on the mobile communication device) will facilitate the transfer.
- a Point-Of-Entry (POE) terminal is also equipped with NFC.
- the POE terminal activates the secure element in the NFC enabled mobile device and triggers an application in the secure element to transfer a ticket, for example, to the POE device which enables the user to gain access to the venue, building, automobile, etc.
- an NFC enabled Point of Sale facilitates a contactless purchase or financial transaction and a Point-of-Entry (POE) terminal facilities contactless access
- an NFC enabled Point of Presence facilitates contactless transaction.
- a POP device is similar to an NFC POS enabled device in that it does contain a secure element and is capable of NFC communications (including two way communications).
- a POP is also capable of induction to be able to power an NFC enabled mobile communication device held in proximity to it and triggers an application running in the secure element to transfer information from the NFC enabled mobile communication device to the POP.
- POPs include a kiosk, automobile, hotel, house, smart poster, smart catalogue, computer, medical device, another NFC mobile device, a music player, products at a retail store, etc.
- a user holds their NFC enabled device near a kiosk which powers the secure element and launches an application to transmit a free song from the kiosk to the secure element.
- the POP can send/receive transaction data to the management server, 180 , have transactions processed by the transaction server 170 , or transfer/receive digital artifacts to/from the secure element 130 at the remote server 210 .
- a POP may be a Smart Poster—When an NFC enabled mobile communication device is held in proximity to a smart poster, the smart poster may transmit information, data, maps, or any other type of digital artifact to the secure element.
- a POP may be a computer, laptop, tablet, etc.
- a user first uses the mobile wallet to select which items to be transferred to the POP and instructs the user to hold the NFC device near the POP.
- the computer can transmit information, data, maps, or any other type of digital artifact to the secure element
- a POP may be another NFC Enabled Mobile communication device.
- a user first uses the mobile wallet to select which items to be transferred to the POP and instructs the user to hold the NFC device near the POP.
- an NFC enabled mobile communication device is held in proximity to another NFC enabled device may transmit contact information, email, web site addresses, social media information, tickets, coupons, receipts, vouchers, content, or any other type of digital artifact to the secure element
- the secure element keys are located at the management server, 180 and may be managed by an entity sometimes referred to as a “Trusted Server Manager”.
- the secure element key may be downloaded to the mobile device in an encrypted file. This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few
- an NFC enabled mobile communication device may have multiple secure elements. There may be a secure element may be dedicated to specific financial transactions vs another secure element which may be dedicated to medical records and have a separate secure element key. There may even be a secure element that is “public domain” which any POS or device can write to without any restricted accesses. As shown in FIG. 7 , there can be a different “health care secure element software application; for different functions. There may be 1 logical secure element or multiple secure elements as described in U.S. patent application U.S. patent Ser. No. 13/213,840, entitled “Transferring Data Between NFC Enabled Mobile Devices With Multiple Secure Elements” filed on Aug. 19, 2011.
- a secure element and application for prescriptions, office visits, appointments, EMR, pictures, etc.
- a user may only need to tap once to transfer artifacts to multiple secure elements.
- a user may tap once to transfer an ID, for example, from the secure element to the POP and then tap another time to transfer artifacts from the POP such as a prescription from the POP to the secure element.
- the transfer of digital artifacts between secure element and a POP is a result each application stored in the secure element having its own Id. So for example, a secure element application that facilitates transfer of a patient's medical ID to/from a secure element may have an ID of “SE_App1.
- a secure element application that facilitates transfer of prescriptions to/from a secure element may have an ID of “SE_App3”.
- SE_App3 an ID of “SE_App3”.
- the applications must be prioritized so that the POP/POS/POE will know which application to trigger and in which order. So, for example if the user selects to get a prescription using their mobile wallet, the mobile wallet will transfer a signal to the secure element to make the “X ray secure element application or SE_App3” the active one and assign it priority of 1 so that the POP/POS/POE will select it first.
- the mobile wallet communicates to the secure element in a number of different ways regardless of whether secure element is internal, inserted into a slot within the body of the mobile device, or affixed externally to the body of a mobile device as described in U.S. Provisional Patent Application No. 61/445,667, entitled “Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011 and U.S. Provisional Patent Application No. 61/429,246, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element using Inaudible Sound Waves,” filed Jan. 3, 2011 both of which are a continuation in part of U.S. patent application Ser. No. 12/948,717, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element,” filed Nov. 17, 2010 which are incorporated by reference herein
- a POP 200 i.e. medical device
- a POP 200 can include secure element that is pre-installed or embedded in the medical device for a wired connection (e.g. USB or serial) or a wireless connection (e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc).
- a wired connection e.g. USB or serial
- a wireless connection e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc.
- the data from the medical can be transmitted to the mobile device 110 coupled to (e.g. the patients mobile device), another mobile device 210 (e.g. the physicians mobile device), server 170 , POS 150 , POE 190 , another POP 200 (e.g.
- the POP 200 i.e. medical device
- a “universal health port” 144 is installed on the medical device using a wired connection such as USB, serial port, or audio port as described in US patent application Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011.
- the POP 200 may be connected to an externally coupled secure element through the universal health port using a wireless connection (e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc).
- a wireless connection e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc.
- the secure element can include WIFI, NFC, Bluetooth, infrared, inaudible sound waves using a speaker and microphone as described in US patent application number, or a combination of these.
- data/digital artifacts can be transferred from the medical device to the secure element using any number of conventional protocols such as USB, Serial Port, NFC, WIFI, Bluetooth, Infrared, inaudible sound waves, etc.
- the data/digital artifacts can be transferred from the secure element to the mobile device 110 coupled to (e.g. the patients mobile device), another mobile device 210 (e.g. the physicians mobile device), server 170 , POS 150 , POE 190 , another POP 200 (e.g.
- the mobile device After the mobile device receives the data/digital artifacts, it can be displayed in the mobile device 110 or the remote mobile device 210 and/or transmitted to another mobile device (e.g. the patients mobile device, the health care provider's mobile device, server,), server, Electronic Medical Records, tablet, another medical device, etc as depicted in FIG. 8 .
- another mobile device e.g. the patients mobile device, the health care provider's mobile device, server,
- server Electronic Medical Records, tablet, another medical device, etc as depicted in FIG. 8 .
- the health care providers NFC enabled mobile device i.e. mobile device with embedded NFC, NFC in a slot, NFC smart sicker
- the medical device secure element application transfers data to the health care providers NFC enabled mobile device as described in U.S. patent application Ser. No. 13/223,233, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011.
- the Health Care Provider's mobile device simply has a secure element with only an NFC transceiver.
- the health care provider When a Health Care Provider wants to extract data from a medical device with the secure element coupled to it, the health care provider “waves” or “holds” their mobile device which only has an NFC transceiver near the medical device with the coupled secure element. In doing so, the secure element coupled to the medical device activates an application running on the health care provider mobile device (not the secure element) which subsequently connects to an application on a remote server for processing.
- the NFC transceiver may simply execute an application stored on a remote server bypassing an application on the mobile device.
- the health care provider's mobile device need not have a full secure element with its own memory and a secure element application.
- the NFC transceiver in the Health Care Provider's mobile device is simply used as a trigger to execute an application either stored on the mobile device and/or stored on a server when it is brought into proximity of a medical device which has a secure element to trigger the NFC transceiver via NFC induction.
- This approach enables the health care provider to utilize applications stored on the management server which is more scalable since the applications that reside on a server can be easily added, changed, etc.
- the Health Care Provider For example, if the Health Care Provider (HCP) wishers to update a patients EMR records stored at the server with the data from the medical device, the Health Care Provider waves their mobile device near the medical device with the coupled secure element and upon doing so, the EMR application on the Health Care Provider mobile device launches and connects to the EMR application on the server to automatically transfer the measurement/sensor data from the medical device to the HCP mobile device and to the server using conventional wireless service.
- HCP Health Care Provider
- digital artifacts can be removed from the secure element coupled to the medical device as described in U as described in U.S. patent application Ser. No. 13/223,233, entitled, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011.
- the mobile wallet which is running on the mobile device/smart phone displays data transmitted from the medical device can include digital artifacts as described in U.S. patent application Ser. No. 11/956,261 entitled “Method and System for Delivering Customized Information To A Mobile Communication Device Based on User Affiliations”, filed Dec. 13, 2007
Abstract
Description
- This application is a continuation in part and claims priority to U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011 which is a continuation in part and claims priority to U.S. patent application Ser. No. 13/216,098 entitled “Streamlining NFC Transactions Using A Mobile Communication Device” filed on Aug. 23, 2011 which is a continuation in part and claims priority to U.S. patent application Ser. No. 13/215,069 entitled “Transferring Data From an NFC Enabled Mobile Device to a Remote Device” filed on Aug. 22, 2011 which is a continuation in part of U.S. patent Ser. No. 13/213,840, entitled “Transferring Data Between NFC Enabled Mobile Devices With Multiple Secure Elements” filed on Aug. 19, 2011 which is a continuation in part and claims priority to U.S. patent Ser. No. 13/208,247, entitled “Transferring Data Between NFC Enabled Mobile Devices” filed on Aug. 11, 2011 which is a continuation in part of U.S. patent Ser. No. 13/184,209, entitled “Method and Systems of loading and unloading digital artifacts between a mobile device with an associated secure element and other remote devices” filed on Jul. 15, 2011 which claims priority to U.S. Provisional Patent Application No. 61/442,384, entitled “Method and Systems of loading and unloading digital between a mobile device with an associated secure element and other remote devices” filed on Feb. 14, 2011. All of the above-referenced patent applications are incorporated by reference herein in their entirety
- Other patents referenced include U.S. patent application Ser. No. 13/223,233, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011, U.S. patent application Ser. No. 11/944,267, entitled “Method and System for Delivering Information to a mobile communication device based on consumer transactions”, filed Nov. 21, 2007 and U.S. patent application Ser. No. 11/956,261 entitled “Method and System for Delivering Customized Information To A Mobile Communication Device Based on User Affiliations”, filed Dec. 13, 2007. All of the above-referenced patent applications are incorporated by reference herein in their entirety
- The present invention relates to data communications and wireless devices.
- Mobile communication devices—e.g., cellular phones, personal digital assistants, and the like—are increasingly being used to conduct payment transaction. Such payment transactions can include, for example, purchasing goods and/or services, tickets, bill payments, and transferring funds between bank accounts. Because of bigger screens, better user input with touch screens increased processing capability, and faster more reliable wireless mobile devices, can be used to manage electronic medical records.
- Medical devices capture and/or store data. Some examples of medical devices included, but are not limited to a medical ID card, Medical ID bracelet, Electronic Medical Records, blood pressure machines, blood glucose, scales, inhalers, INR, prescription bottles and trays, pulse oximeter, or any device that captures and stores medical data. However, medical devices don't export data or not very easily. So, the Health Care Provider (HCP) is required to manually write down the sensor/measurement data displayed on the medical device and/or enter it into a computer which is time consuming, prone to error, and costly.
- While some medical devices have the ability to export data to a personal computer using a cable or wirelessly using blue tooth for example, these few devices have special customized interfaces which are costly and limit the patient and health care provider to using those devices which may not be their preferred medical device. In many instances patients and health care providers prefer to use certain medical devices based on their functionality, cost, or accuracy in capturing measurement data particularly for very serious chronic illnesses where accuracy is extremely important.
- This invention describes various ways to capture data from any medical device and transmit it electronically to mobile devices (e.g. cell phones, smart phones, electronic note books), computers, servers, electronic medical records, etc. by using a secure element that serves as a “universal health port”. Thus, making a solution that is more scalable, flexible, cost effective, and beneficial to patients, health care providers, etc.
- This application is a continuation in part and claims priority to U.S. patent application Ser. No. 13/216,098 entitled “Streamlining NFC Transactions Using A Mobile Communication Device” filed on Aug. 23, 2011 which is a continuation in part and claims priority to U.S. patent application Ser. No. 13/215,069 entitled “Transferring Data From an NFC Enabled Mobile Device to a Remote Device” filed on Aug. 22, 2011 which is a continuation in part of U.S. patent Ser. No. 13/213,840, entitled “Transferring Data Between NFC Enabled Mobile Devices With Multiple Secure Elements” filed on Aug. 19, 2011 which is a continuation in part and claims priority to U.S. patent Ser. No. 13/208,247, entitled “Transferring Data Between NFC Enabled Mobile Devices” filed on Aug. 11, 2011 which is a continuation in part of U.S. patent Ser. No. 13/184,209, entitled “Method and Systems of loading and unloading digital artifacts between a mobile device with an associated secure element and other remote devices” filed on Jul. 15, 2011 which claims priority to U.S. Provisional Patent Application No. 61/442,384, entitled “Method and Systems of loading and unloading digital between a mobile device with an associated secure element and other remote devices” filed on Feb. 14, 2011. All of the above-referenced patent applications are incorporated by reference herein in their entirety
- The system is configured with a mobile device (with client application also referred to as a mobile wallet), a secure element that is associated with the mobile device, NFC Point Of Sale System which is capable of processing financial transactions (including 2-way wireless terminal capable of sending and transmitting), NFC Point-Of-Presence Terminal which is capable of processing non-financial transactions (including 2-way wireless terminal capable of sending and transmitting), an NFC Point-of-Entry Device which is capable of providing access to venues including 2-way wireless terminal capable of sending and transmitting, a management server, a Trusted Service Manager (TSM) and several 3rdParty artifact provider/aggregator.
- In the delivery scenario, when the user holds an NFC enabled mobile communication device with a secure element coupled to it in proximity of a suitable equipped POS/POE/POP with NFC, the NFC POS/POE/POP device will trigger an application residing in the secure element (which is different than an application residing on the mobile communication device) to power on and activate an application residing in the secure element, transfer data or digital artifacts (e.g debit/prepaid/credit card, receipts, tickets, advertisements, coupons, loyalty points, gift cards, vouchers, content (video, image, ringtone, movie), games, documentation, business cards, tickets, hotel key, health care records, security key, automobile key, etc.) from/to the secure element, and the secure element may issue commands and/or respond to commands just to name a few. Using this system, at the time of a transaction, a user can use the mobile wallet software (on a mobile computing device) and associated secure element, in conjunctions with the POP/POS/POE to:
-
- Store medical ID
- Store patient contact information such as address, phone number, employer contact info
- Store emergency contact information
- Store basic patient information such as gender, age, date of birth, blood type, race, etc
- Store physician names and contact information
- Store allergies
- Store a list of vaccinations
- Store vital signs such as temperature, blood pressure, pulse, respiratory rate, “pain” level, glucose level, cholesterol, height, weight, etc
- Store insurance information including list of approved doctors approved labs, approved drugs, approved generic drugs, health care coverage, out of pocket costs, co-pay costs
- Payment methods—credit, debit, prepaid, checking account number
- Store prescriptions
- Store doctors' orders for use of prescriptions
- Pay for prescriptions
- Store XRays
- Store lab results
- Pay for lab tests
- Store hospital ID bracelet
- Store medication used in hospital
- Schedule of doctor appointments
- Store organ status and donor information
- Transfer digital medical artifacts (e.g medical ID, basic patient information, patient contact information, emergency contact information, primary care physician information, health insurance information including co-pay and deductibles, prescriptions, office visit summary, appointment cards, Electronic Medical Records (EMR), lab results, blood type, organ/donor status, vital signs, diagnostic data, immunization records, payments and transaction history, pictures, etc) to remote devices
- Some of the challenges that an NFC enabled mobile device can address include, but are not limited to the following use cases:
- Elderly/Senior Citizens-They may have a sudden health care need with a sensitive need to have a list of medical information, allergies, and prescriptions readily available for urgent health care. Care givers may not have access to their medical information.
- ER Patients Their identity may not be known when they arrive at ER and require emergency medical treatment. So, it is urgent to identify who they are, medical history, allergies, and prescriptions, etc.
- New Patients—If a new patient is visiting a new doctor for a diagnosis and potentially time sensitive, treatment, patients will need to have medical information, allergies, and prescriptions readily available which may take weeks to receive from previous physician.
- Children—Children may not have an ID with them and be on a field trip, sporting event, camping trip, friend's house, etc. So, if there is a health issue, it will be important to be able to confirm their identity, medical information, allergies, and prescriptions readily available for urgent health care, etc.
- Frequent international travelers—Frequent travelers need to track their shots and immunizations for travel abroad. If they may have a sudden health care need, they will need to have access to medical information, allergies, and prescriptions readily available for urgent health care.
- Patients with Alzheimer's or other conditions that impact memory. They may get lost and not remember who they are or how to get back home or have any identification with them. So, they health care professionals will need to be able to identify them as well as their medical history, allergies, and prescriptions readily available for urgent health care.
- Critically serious patients in ICU or prenatal may have require very specific medications and dosages.
- Patients who require daily or constant monitoring for insulin levels, asthma, high blood pressure, heart pace maker, etc.
- This invention enables patients and health care professionals (nurse, doctor, pharmacist, etc) to manage digital medical artifacts medical digital artifacts (e.g. medical ID, basic patient information, patient contact information, emergency contact information, primary care physician information, health insurance information including co-pay and deductibles, prescriptions, office visit summary, appointment cards, Electronic Medical Records (EMR), lab results, blood type, organ/donor status, vital signs, diagnostic data, immunization records, payments and transaction history, pictures, etc) using an NFC enabled mobile device. This is accomplished when the user holds, “waves”, or “taps” their NFC enabled device in proximity to an NFC Point-Of-Presence (POP) device, Point-Of-Entry (POE), Point-Of-Sale (POS) device, smart poster, or another NFC enabled device. Upon doing so, the POP/POE/POS/etc activates the secure element associated with the NFC enabled mobile device and powers the secure element through induction. So, the secure element need not have its own power source nor does the secure element require use of the battery inside of the mobile device. Correspondingly, if the battery in the mobile device is dead, the user may not be able to use the mobile device to place a phone call, receive an SMS, or surf the web, but they will be able to transfer information from their secure element (e.g. medical ID) since the secure element is powered by the remote NFC enabled POP/POS/POE device. The secure element can also receive digital artifacts from a POP/POS/POE device such as Xrays, prescriptions, appointment cards, etc even if the battery inside of the mobile communication device lacks power. This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few.
-
FIG. 1 illustrates a block diagram of a communication system including a wireless mobile communication device and a management server in accordance with one implementation. -
FIG. 2 illustrates a block diagram of a mobile communication device in accordance with one implementation. -
FIG. 3 illustrates a block diagram of a secure element in accordance with one implementation. - FIGS. 2B1, 2B2A, 2B2B illustrate more details regarding certain components illustrated in
FIG. 1 . -
FIG. 3 illustrates a secure element embedded in an ID card -
FIG. 4 illustrates a secure element embedded in a wristband -
FIG. 5 illustrates more details regarding certain components of a secure illustrated inFIG. 1 of a secure element that is capable of bi-directional communication with a mobile device and transfer of data to a remote server -
FIG. 6 illustrates multiple secure elements coupled to a mobile communication device -
FIG. 7 illustrates secure element applications -
FIG. 8 illustrates medical devices with an externally affixed secure element - Reference will now be made in detail to various embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present inventions. However, it will be apparent to one of ordinary skill in the art that the present inventions may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
- An NFC enabled device is one that includes a secure element and enables contactless transactions which have been described in more detail in previous patents including U.S. patent application Ser. No. 13/184,246, entitled “Using a mobile device to enable purchase of deals and increase customer loyalty” filed on Jul. 15, 2011, U.S. Provisional Patent Application No. 61/445,667, entitled “Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011 and U.S. Provisional Patent Application No. 61/429,246, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element using Inaudible Sound Waves,” filed Jan. 3, 2011 both of which are a continuation in part of U.S. patent application Ser. No. 12/948,717, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element,” filed Nov. 17, 2010, U.S. patent application Ser. No. 12/592,581 entitled “Method and Apparatus For Completing A Transaction Using A Wireless Mobile Communication Channel and Another Communication Channel”, filed Nov. 25, 2009, U.S. patent application Ser. No. 11/948,903, entitled “Method And System For Conducting An Online Payment Transaction Using A Mobile Communication Device” filed on Nov. 30, 2007, U.S. patent application Ser. No. 11/939,821, entitled “Method and System for Securing Transactions Made Through a Mobile Communication Device” filed Nov. 14, 2007, and U.S. patent application Ser. No. 11/933,351 entitled “Method and System for Purchasing Event Tickets Using a Mobile Communication Device”, filed Oct. 31, 2007, and U.S. patent application Ser. No. 11/933,321 entitled “Method and System for Adapting a Wireless Mobile Communication Device for Wireless Transactions,” filed Oct. 31, 2007 all of which are a continuation-in-part of U.S. patent application Ser. No. 11/467,441, entitled “Method and Apparatus for Completing a Transaction Using a Wireless Mobile Communication Channel and Another Communication Channel,” filed Aug. 25, 2006, which claims priority to U.S. Provisional Patent Application Nos. 60/766,171 and 60/766,172, both of which were filed Dec. 31, 2005. All of the above-referenced patent applications are incorporated by reference herein in their entirety.
- As previously described in U.S. patent application Ser. No. 12/592,581, entitled “Method and Apparatus For Completing A Transaction Using A Wireless Mobile Communication Channel and Another Communication Channel”, filed Nov. 25, 2009 which is a continuation in part of U.S. patent application Ser. No. 11/467,441, entitled “Method and Apparatus For Completing A Transaction Using A Wireless Mobile Communication Channel and Another Communication Channel”, filed Aug. 25, 2006,
FIG. 1 is a block diagram illustrating a communication system 100 in accordance with some embodiments. The communication system 100 includes a hand-held, wirelessmobile communication device 110 with anantenna 120 for wireless communication. While theantenna 120 is shown as extending from themobile communication device 110 for visual clarity, theantenna 120 may be implemented internally within themobile communication device 110. Also, themobile communication device 110 may include more than oneantenna 120. Themobile communication device 110 includes a user interface for entering data. For example, a display 124 (FIG. 2 ) is a touch-screen display; alternatively or in addition, themobile communication device 110 includes a keypad 125 (FIG. 2 ) for entering data. - A preferred embodiment, both the
radio element 120 and thesecure element 130 are both disposed internally within a body of themobile device 110 as illustrated inFIG. 1 , although in certain embodiments thesecure element 130 can be external to themobile device 110 as described hereinafter. In a variant implementation, themobile device 110 contain a slot, which allows for the insertion of asecure element 130 into a slot and thus the physical insertion, mechanical and electrical connection as needed. In this configuration, the secure element can be purchased independently of themobile device 110. Thesecure element 130 can also be disposed into a slot that only provides for physical insertion and mechanical connection to the body of themobile device 110, and can then preferably include a transceiver that allows for the communication with theradio element 130 using a wireless local communication channel. - The
radio element 120 also is illustrated as optionally including anothertransceiver 129, such as a Bluetooth or WIFI transceiver, which can transmit and receive signals with an external device and then communicate signals to and from theradio processor 123. This additional communication channel allows for communications between other external devices, such as an external Bluetooth enabled smartcard, and provides an additional communication channel that is useful for certain transactions, as described further herein. - FIG. 2B1 illustrates a preferred embodiment of the
secure element 130 associated with themobile device 110, thesecure element 130 being commonly known as a smart card. As illustrated, thesecure element 130 has asecure processor 132, asecure memory 133 and a POS/NFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel. Thesecure processor 132 communicates via thesecure element driver 128 with theradio processor 123, using, as mentioned above, signals described in the Java Card 2.1 Platform API Specification. The transaction request signals and the transaction response signals associated with the transaction preferably include identification code associated with the user, as well as information relative to the transaction, such as item, quantity, vendor, as is known. ThePOS transceiver 134 is preferably an NFC device of some type, which uses an NFC modem, although it can also be a Bluetooth, WIFI or other transceiver. In the case of the implementation of the POS transceiver being an NFC modem, such an NFC modem will typically have a set of registers that can be read/written by thesecure processor 132. These registers are in turn available for reading and writing over the RFID communications channel and serve as a sort of shared memory between thesecure processor 123 within thesecure element 130 and the RFID reader that is associated with thePOS terminal 150. This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few. - Illustrated in an alternative embodiment is the inclusion of a radio/Bluetooth/
WIFI transceiver 136, which can communicate with other devices, such as a transceiver associated with theradio processor 120 or for other external devices having those communication capabilities, thus allowing for more flexibility. - FIG. 2B2A shows a modified
secure element 130, in which theradio element 120 does not communicate with the secure element through asecure element driver 128 of some type. In this case, for example, thesecure element 130 may be external to themobile device 110 and as such is not connected to the radio element through thesecure element driver 128. In such an implementation, however, if thetransceiver 136 as described above is included, and asimilar transceiver 129 associated with theradio element 130 as described previously with respect toFIG. 1 is included, then this communication channel can be used to wirelessly obtain direct communications between theradio element 120 and thesecure element 130. - This implementation allows for certain bidirectional communications with other devices, as well as with the
radio element 120, and as such more functionality and flexibility is achieved. This implementation is particularly useful since it establishes a direct local communication path with theradio element 120, since there is not communications with theradio element 120 via the path ofdriver 128. - If either of the
transceivers respective radio element 120 orsecure element 130, and there is no direct connection between theradio element 120 an thesecure element 130, then a direct communication link between theradio element 120 an thesecure element 130 will not exist. As such, while ticketing and many transactions can still exist, data from a real-time transaction performed using thesecure element 130 cannot be made directly available to the radio processor and the applications stored thereon, which can prevent, for example, certain redundancy checks to occur, such as a ticketing application in which, after the ticket order has been placed, the ticketing application in thememory 126 associated with theradio element 130 can be programmed to provide an alert if the ticket receipt, via themanagement server 180, has not been received within a certain period of time. Such an alert would not be possible to program directly (although it could be programmed indirectly via the button panel on the phone, though such an implementation requires extra user intervention, which, if possible, one attempts to avoid in transactions such as this. - FIG. 2B2B shows a modified
secure element 130″, in which the secure element does not include a processor that is capable of bidirectional communications, but instead is apassive device 138′, such as an RFID sticker or some other tag, that allows for a user identification, such that a transaction that is initiated with thepassive device 138′ will cause themanagement server 180 to perform the transaction details. In this implementation, the code received from thePOS terminal 150 or thePOE terminal 190 is transmitted from thePOS terminal 150 or thePOE terminal 190 to themanagement server 180, which then takes over the transaction. Thispassive device 138′, with the identification code stored thereon, can thus be associated with amobile device 110 not otherwise equipped for such communications, and themanagement server 190 can provide transactional information to themobile device 110 using available channels on the mobile device (such as audio, sms or other known data transmission methods). While bidirectional communications do not occur with other devices, transactions are possible, because themanagement server 190 is involved. - FIG. 2B2C illustrates a secure element that is capable of either two-way communication or one-way communication with a POS/POE device that is not affixed to a mobile device nor electrically coupled to the mobile device. Instead the secure element is affixed to a hospital bracelet.
FIG. 3 illustrates a secure element that is affixed to a affixed to a plastic medical ID card andFIG. 4 illustrates a secure element affixed to a affixed to a hospital bracelet, for example. Similarly, a secure element that is not affixed to a mobile device nor is electrically coupled to a mobile device can be incorporated with a key chain, watch, ring, bracelet worn as jewelry. - As illustrated in
FIG. 5 , and enhancedsecure element 130 that is capable of bidirectional communication with a mobile device has asecure NFC processor 132, asecure memory 133 and a POS/NFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel. A/D converter 135, amicrophone 137, aspeaker 139, and a,cable 141, power harvester, 144, Long range RF transceiver, 146, and a SE controller, 148. TheSecure Element Controller 148 can either be logical or physical. In a logical implementation, it simply utilizes the primarysecure element transceiver 134,memory 133 with data and applications, and aprocessor 132 to communicate with multiple logical or physical secure elements. Stated another way, the Secure Element Controller is the parent controller and all of the other logical or physical secure elements. The Secure Element Controller can issue read/write commands to all of the other logical or physical secure elements. - As described above, the
secure element 130 has asecure processor 132, asecure memory 133 and a POS orNFC transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel. In some embodiments asecure element 130 is internal to themobile communication device 110. In some embodiments, thesecure element 130 is externally attached to themobile communication device 110. For example, thesecure element 130 is adhesively affixed or mechanically secured to the housing of themobile communication device 110. Alternatively, thesecure element 130 is housed within a slot in themobile communication device 110. Thesecure element 130 includes an antenna 131 for wireless communication. While the antenna 131 is shown as extending from thesecure element 130 for visual clarity, the antenna 131 may be implemented internally within thesecure element 130. Also, thesecure element 130 may include more than one antenna 131. Communication occurs wirelessly between thesecure element 130 and themobile communication device 110 viarespective antennas 120 and 131, over a direct wireless channel 163 between themobile communication device 110 and thesecure element 130. Thus, in some embodiments, the channel 163 does not pass through a network. - The point of
sale terminal 150 illustrated inFIG. 1 is conventional, in that it has the capability of electronically reading information from a device equipped to transmit information in a format that it reads. Thus, the reader (not shown) within the point ofsale terminal 150 can be of one or many types. If the point of sale terminal reader (not shown) includes the provision for NFC communications, then simply bringing thesecure element 130 with the NFC transceiver will cause initiation of a transaction and the transmission of the identification code associated with thesecure element 130 and thus the user. - For the embodiments described above, various software that is downloaded into the
memory 126 of theradio element 120 and thesecure memory 132 of thesecure element 130, along with software resident on themanagement server 180, will cooperate at a layer that is above the physical layer of the communications, in order for the desired transaction to occur. This software is implemented using based upon known knowledge ofmobile device 110 internals and application platforms, NFC, smartcard internals and application platforms, payment protocols (e.g. PayPass), and the working/workflow associated with POS and POE terminals, and the transaction and management servers. In addition, the present invention provides for piggybacking a tunneling protocol on top of the payment protocol, so that thesecure elements 130 can communicate with thetransaction server 170 and/or themanagement server 180, without modification to thePOS terminal 150 or thePOE terminal 190. As such, this includes software within thesecure element 130 that embeds the required information in fields which will not adversely affect the performance of thePOS terminal 150 and/or thePOE terminal 190, and also software intransaction server 170 that will extract the piggybacked payload, associate the payload with themanagement server 180 if needed, and then authenticate, authorize, and execute transfers of transaction information to themanagement server 180. - In another embodiment, the piggybacked payload is sent, instead of to the
transaction server 170, to themanagement server 180, which can then associate the transaction and notify thetransaction server 170, thePOS terminal 150 and/or the POE terminal as needed. - There are several types of NFC transactions. First, when the secure element is held in proximity to a remote device (i.e. Point-Of-Sale (POS)
device 150, Point-Of-Entry (POE) 190, Point-Of-Presence (POP)device 200, smart poster, another secure element, etc) the POS/POE/POP activates or powers thesecure element 130 through induction and triggers an application residing in the secure element (which is different than an application residing on the mobile communication device. So, the secure element need not have its own power source nor does the secure element require use of the battery inside of the mobile device. Stated another way, if the battery in the mobile device is dead, the user may not be able to use the mobile device to place a phone call, receive an SMS, or surf the web, but they will be able to purchase item and receive coupons and other digital artifacts using the secure element since the secure element is powered by the remote NFC enabled POS/POE/POP device. To reiterate, after triggering the secure element, an application residing in the secure element (which is different than an application residing on the mobile communication device) is launched and the application can transfer digital artifacts to the POS/POE/POP and the POS/POE/POP terminal can transmit digital artifacts to the secure element again even if the battery inside of the mobile communication device lacks power. There are instances when the NFC enabled mobile device is active and it can power any NFC device in passive mode including a POS/POE/POP, smart poster, or another NFC enabled mobile device which will described in more detail further herein. - While a POS may receive payment credentials from the secure element which is processed by the
transaction server 170, the POS may transfer a coupon, receipt, or some other digital artifact to the secure element simultaneously during the induction process from thePOS terminal 150, thetransaction server 170 or themanagement server 180. Stated another way, the user need only hold, “wave” or “tap” their NFC enabled device once near the POS and both the transmission of the ticket to the POP and the receipt of the digital artifact will occur simultaneously so the user will not have to “tap” or “wave” their phone twice. This is accomplished through induction as well. The POS device/terminal will activate the secure element and an application residing in the secure element (which is different than an application residing on the mobile communication device) will facilitate the transfer. - As mentioned previously a Point-Of-Entry (POE) terminal is also equipped with NFC. When a user holds, “waves”, or “taps” their NFC enabled device near a POE terminal, the POE terminal activates the secure element in the NFC enabled mobile device and triggers an application in the secure element to transfer a ticket, for example, to the POE device which enables the user to gain access to the venue, building, automobile, etc.
- While an NFC enabled Point of Sale (POS) facilitates a contactless purchase or financial transaction and a Point-of-Entry (POE) terminal facilities contactless access, an NFC enabled Point of Presence (POP) facilitates contactless transaction. A POP device is similar to an NFC POS enabled device in that it does contain a secure element and is capable of NFC communications (including two way communications). A POP is also capable of induction to be able to power an NFC enabled mobile communication device held in proximity to it and triggers an application running in the secure element to transfer information from the NFC enabled mobile communication device to the POP. Some examples of POPs include a kiosk, automobile, hotel, house, smart poster, smart catalogue, computer, medical device, another NFC mobile device, a music player, products at a retail store, etc. One example is a user holds their NFC enabled device near a kiosk which powers the secure element and launches an application to transmit a free song from the kiosk to the secure element. The POP can send/receive transaction data to the management server, 180, have transactions processed by the
transaction server 170, or transfer/receive digital artifacts to/from thesecure element 130 at theremote server 210. - A POP may be a Smart Poster—When an NFC enabled mobile communication device is held in proximity to a smart poster, the smart poster may transmit information, data, maps, or any other type of digital artifact to the secure element.
- A POP may be a computer, laptop, tablet, etc. A user first uses the mobile wallet to select which items to be transferred to the POP and instructs the user to hold the NFC device near the POP. When an NFC enabled mobile communication device is held in proximity to the computer, the computer can transmit information, data, maps, or any other type of digital artifact to the secure element
- A POP may be another NFC Enabled Mobile communication device. A user first uses the mobile wallet to select which items to be transferred to the POP and instructs the user to hold the NFC device near the POP. When an NFC enabled mobile communication device is held in proximity to another NFC enabled device may transmit contact information, email, web site addresses, social media information, tickets, coupons, receipts, vouchers, content, or any other type of digital artifact to the secure element
- As described in U.S. patent application Ser. No. 13/213,840 entitled “Transferring Data Between NFC Enabled Mobile Devices With Multiple Secure Elements” filed on Aug. 19, 2011 which is incorporated herein by reference, after a user holds an NFC enabled mobile device in proximity to an NFC POS/POE/POP, the NFC POS/POE/POP can transfer secondary digital artifacts to the secure element such as Xrays, tickets, business cards, music, product information, etc. As described in more detail in the patent applications mentioned above, a user may have to authenticate and the secure element may have to be unlocked prior to the storage of digital artifacts in the secure element. For security purposes, the secure element keys are located at the management server, 180 and may be managed by an entity sometimes referred to as a “Trusted Server Manager”. In cases where network availability is not reliable and performance is critical, the secure element key may be downloaded to the mobile device in an encrypted file. This communication is specified, for example, in the ISO 14443A/B standard and ISO 15693 just to name a few
- As mentioned previously, an NFC enabled mobile communication device may have multiple secure elements. There may be a secure element may be dedicated to specific financial transactions vs another secure element which may be dedicated to medical records and have a separate secure element key. There may even be a secure element that is “public domain” which any POS or device can write to without any restricted accesses. As shown in
FIG. 7 , there can be a different “health care secure element software application; for different functions. There may be 1 logical secure element or multiple secure elements as described in U.S. patent application U.S. patent Ser. No. 13/213,840, entitled “Transferring Data Between NFC Enabled Mobile Devices With Multiple Secure Elements” filed on Aug. 19, 2011. There may be a secure element and application for prescriptions, office visits, appointments, EMR, pictures, etc. A user may only need to tap once to transfer artifacts to multiple secure elements. Alternatively, a user may tap once to transfer an ID, for example, from the secure element to the POP and then tap another time to transfer artifacts from the POP such as a prescription from the POP to the secure element. The transfer of digital artifacts between secure element and a POP is a result each application stored in the secure element having its own Id. So for example, a secure element application that facilitates transfer of a patient's medical ID to/from a secure element may have an ID of “SE_App1. In contrast, a secure element application that facilitates transfer of prescriptions to/from a secure element may have an ID of “SE_App3”. Whenever multiple applications exist in the secure element, the applications must be prioritized so that the POP/POS/POE will know which application to trigger and in which order. So, for example if the user selects to get a prescription using their mobile wallet, the mobile wallet will transfer a signal to the secure element to make the “X ray secure element application or SE_App3” the active one and assign it priority of 1 so that the POP/POS/POE will select it first. The mobile wallet communicates to the secure element in a number of different ways regardless of whether secure element is internal, inserted into a slot within the body of the mobile device, or affixed externally to the body of a mobile device as described in U.S. Provisional Patent Application No. 61/445,667, entitled “Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011 and U.S. Provisional Patent Application No. 61/429,246, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element using Inaudible Sound Waves,” filed Jan. 3, 2011 both of which are a continuation in part of U.S. patent application Ser. No. 12/948,717, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element,” filed Nov. 17, 2010 which are incorporated by reference herein - In one embodiment, a POP 200 (i.e. medical device) can include secure element that is pre-installed or embedded in the medical device for a wired connection (e.g. USB or serial) or a wireless connection (e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc). In this way, the data from the medical can be transmitted to the
mobile device 110 coupled to (e.g. the patients mobile device), another mobile device 210 (e.g. the physicians mobile device),server 170,POS 150,POE 190, another POP 200 (e.g. medical, EMR) using USB, Serial Port, NFC, WIFI, Bluetooth, Infrared, inaudible sound as described in US patent application Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011, U.S. patent application Ser. No. 13/223,233, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011. - In another embodiment, the POP 200 (i.e. medical device) may be connected to an externally coupled secure element through a “universal health port” 144 is installed on the medical device using a wired connection such as USB, serial port, or audio port as described in US patent application Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011.
- Alternatively, the POP 200 (i.e. medical device) may be connected to an externally coupled secure element through the universal health port using a wireless connection (e.g. NFC, Bluetooth, WIFI, infrared, inaudible sound waves using a speaker and microphone, etc). as described in U.S. Provisional Patent Application No. 61/429,246, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element using Inaudible Sound Waves,” filed Jan. 3, 2011 both of which are a continuation in part of U.S. patent application Ser. No. 12/948,717, entitled “Wireless Bidirectional Communications between a Mobile Device and Associated Secure Element,” filed Nov. 17, 2010, or some other conventional port. The secure element can include WIFI, NFC, Bluetooth, infrared, inaudible sound waves using a speaker and microphone as described in US patent application number, or a combination of these.
- In either case regardless of whether the POP, 200 (i.e. medical device) has an embedded secure element or a coupled secure element connected to the universal health port using a wired connection or a wireless connection, data/digital artifacts can be transferred from the medical device to the secure element using any number of conventional protocols such as USB, Serial Port, NFC, WIFI, Bluetooth, Infrared, inaudible sound waves, etc. Once the data/digital artifacts are at the secure element, they can be transferred from the secure element to the
mobile device 110 coupled to (e.g. the patients mobile device), another mobile device 210 (e.g. the physicians mobile device),server 170,POS 150,POE 190, another POP 200 (e.g. medical, EMR) using USB, Serial Port, NFC, WIFI, Bluetooth, Infrared, inaudible sound as described in US Patent application Non-Wireless Bidirectional Communication Between a Mobile Device and Associated Secure Element using an Audio Port” filed on Feb. 23 2011, U.S. patent application Ser. No. 13/223,233, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011″ and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011. - After the mobile device receives the data/digital artifacts, it can be displayed in the
mobile device 110 or the remotemobile device 210 and/or transmitted to another mobile device (e.g. the patients mobile device, the health care provider's mobile device, server,), server, Electronic Medical Records, tablet, another medical device, etc as depicted inFIG. 8 . - In one embodiment, when a Health Care Provider wants to extract data from a medical device using NFC, the health care providers NFC enabled mobile device (i.e. mobile device with embedded NFC, NFC in a slot, NFC smart sicker) powers or activates the secure element application located inside the secure element of the medical device which has either an embedded NFC or externally coupled secure element. In doing so, the medical device secure element application transfers data to the health care providers NFC enabled mobile device as described in U.S. patent application Ser. No. 13/223,233, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011.
- In another embodiment, the Health Care Provider's mobile device simply has a secure element with only an NFC transceiver. When a Health Care Provider wants to extract data from a medical device with the secure element coupled to it, the health care provider “waves” or “holds” their mobile device which only has an NFC transceiver near the medical device with the coupled secure element. In doing so, the secure element coupled to the medical device activates an application running on the health care provider mobile device (not the secure element) which subsequently connects to an application on a remote server for processing. Alternatively, the NFC transceiver may simply execute an application stored on a remote server bypassing an application on the mobile device. In this way, the health care provider's mobile device need not have a full secure element with its own memory and a secure element application. Stated another way, the NFC transceiver in the Health Care Provider's mobile device is simply used as a trigger to execute an application either stored on the mobile device and/or stored on a server when it is brought into proximity of a medical device which has a secure element to trigger the NFC transceiver via NFC induction. This approach enables the health care provider to utilize applications stored on the management server which is more scalable since the applications that reside on a server can be easily added, changed, etc.
- For example, if the Health Care Provider (HCP) wishers to update a patients EMR records stored at the server with the data from the medical device, the Health Care Provider waves their mobile device near the medical device with the coupled secure element and upon doing so, the EMR application on the Health Care Provider mobile device launches and connects to the EMR application on the server to automatically transfer the measurement/sensor data from the medical device to the HCP mobile device and to the server using conventional wireless service.
- In cases where security is required to capture and transfer the data, the techniques described as described in U.S. patent application Ser. No. 13/223,233, entitled “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011.
- In some embodiments, digital artifacts can be removed from the secure element coupled to the medical device as described in U as described in U.S. patent application Ser. No. 13/223,233, entitled, “Using an NFC Enabled Mobile Device To Manage Health Care” filed on Aug. 31, 2011” and U.S. patent application Ser. No. 13/218,879 entitled “Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts” filed on Aug. 26, 2011.
- In some embodiments, the mobile wallet which is running on the mobile device/smart phone displays data transmitted from the medical device can include digital artifacts as described in U.S. patent application Ser. No. 11/956,261 entitled “Method and System for Delivering Customized Information To A Mobile Communication Device Based on User Affiliations”, filed Dec. 13, 2007
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/078,440 US10892044B2 (en) | 2011-02-14 | 2013-11-12 | Connected medical devices |
US17/142,975 US11769574B2 (en) | 2011-02-14 | 2021-01-06 | Transmitting medical digital artifacts to a mobile device |
US18/372,550 US20240038345A1 (en) | 2011-02-14 | 2023-09-25 | Blaze transmission of medical digital artifacts to a mobile device |
Applications Claiming Priority (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161442384P | 2011-02-14 | 2011-02-14 | |
US201113184209A | 2011-07-15 | 2011-07-15 | |
US201113208247A | 2011-08-11 | 2011-08-11 | |
US201113213840A | 2011-08-19 | 2011-08-19 | |
US201113215069A | 2011-08-22 | 2011-08-22 | |
US201113216098A | 2011-08-23 | 2011-08-23 | |
US13/218,879 US20180130548A1 (en) | 2011-02-14 | 2011-08-26 | Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts |
US14/078,440 US10892044B2 (en) | 2011-02-14 | 2013-11-12 | Connected medical devices |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/218,879 Continuation US20180130548A1 (en) | 2011-02-14 | 2011-08-26 | Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/142,975 Continuation US11769574B2 (en) | 2011-02-14 | 2021-01-06 | Transmitting medical digital artifacts to a mobile device |
Publications (3)
Publication Number | Publication Date |
---|---|
US20150134358A1 US20150134358A1 (en) | 2015-05-14 |
US20180144096A9 true US20180144096A9 (en) | 2018-05-24 |
US10892044B2 US10892044B2 (en) | 2021-01-12 |
Family
ID=53044535
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/078,440 Active 2032-10-22 US10892044B2 (en) | 2011-02-14 | 2013-11-12 | Connected medical devices |
US17/142,975 Active 2032-03-15 US11769574B2 (en) | 2011-02-14 | 2021-01-06 | Transmitting medical digital artifacts to a mobile device |
US18/372,550 Pending US20240038345A1 (en) | 2011-02-14 | 2023-09-25 | Blaze transmission of medical digital artifacts to a mobile device |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/142,975 Active 2032-03-15 US11769574B2 (en) | 2011-02-14 | 2021-01-06 | Transmitting medical digital artifacts to a mobile device |
US18/372,550 Pending US20240038345A1 (en) | 2011-02-14 | 2023-09-25 | Blaze transmission of medical digital artifacts to a mobile device |
Country Status (1)
Country | Link |
---|---|
US (3) | US10892044B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109102853A (en) * | 2018-08-30 | 2018-12-28 | 武汉携康智能健康设备有限公司 | A kind of health management system arranged and method based on Internet of Things and cloud computing |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9168340B2 (en) | 2009-03-27 | 2015-10-27 | Bing Innovations, Llc | System and method for pain reduction during skin puncture and breakable tip therefor |
US9463287B1 (en) * | 2004-09-20 | 2016-10-11 | Bing Innovations, Llc | Controlling usage of replaceable tool ends |
WO2010110823A1 (en) | 2009-03-27 | 2010-09-30 | Bing Innovations, Llc | Apparatus and method for reducing pain during skin puncturing procedures |
US9600676B1 (en) * | 2014-06-16 | 2017-03-21 | Verily Life Sciences Llc | Application-level wireless security for wearable devices |
KR20160109151A (en) * | 2015-03-10 | 2016-09-21 | 노틸러스효성 주식회사 | Apparatus and method for processing a transaction for receiving and paying cash |
US10695508B2 (en) | 2015-05-01 | 2020-06-30 | Bing Innovations, Llc | Reducing pain of skin piercing using vibration |
KR102641177B1 (en) | 2015-07-20 | 2024-02-26 | 펄 테라퓨틱스 인코포레이티드 | Aerosol delivery systems and related methods |
US11030591B1 (en) * | 2016-04-01 | 2021-06-08 | Wells Fargo Bank, N.A. | Money tracking robot systems and methods |
WO2018152241A1 (en) * | 2017-02-15 | 2018-08-23 | Abbott Diabetes Care Inc. | Systems, devices, and methods for integration of an analyte data reader and medication delivery device |
CN108447535A (en) * | 2018-03-02 | 2018-08-24 | 河南中医药大学 | A kind of obstetrical and gynecological disease Medical treatment control system Internet-based |
US11094158B2 (en) | 2018-08-08 | 2021-08-17 | Carefusion 303, Inc. | Mobile system for dispensing medication |
WO2020160326A1 (en) * | 2019-01-30 | 2020-08-06 | The Regents Of The University Of Colorado, A Body Corporate | Health sticker: a modular adhesive platform monitoring vital signals |
US10955941B2 (en) * | 2019-03-26 | 2021-03-23 | Atlantic Health System, Inc. | Multimodal input device and system for wireless record keeping in a multi-user environment |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7256708B2 (en) * | 1999-06-23 | 2007-08-14 | Visicu, Inc. | Telecommunications network for remote patient monitoring |
US7060030B2 (en) * | 2002-01-08 | 2006-06-13 | Cardiac Pacemakers, Inc. | Two-hop telemetry interface for medical device |
GB0211644D0 (en) * | 2002-05-21 | 2002-07-03 | Wesby Philip B | System and method for remote asset management |
US7494055B2 (en) | 2002-09-17 | 2009-02-24 | Vivotech, Inc. | Collaborative negotiation techniques for mobile personal trusted device financial transactions |
FR2855456B1 (en) * | 2003-05-28 | 2006-11-03 | Mavic Sa | BIKE FOR USE IN CYCLING PRACTICE AND WHEEL FOR USE ON SUCH A BIKE |
US7502498B2 (en) * | 2004-09-10 | 2009-03-10 | Available For Licensing | Patient monitoring apparatus |
US7128274B2 (en) | 2005-03-24 | 2006-10-31 | International Business Machines Corporation | Secure credit card with near field communications |
EP1722310A1 (en) * | 2005-04-12 | 2006-11-15 | Roche Diagnostics GmbH | Medical software download to mobile phone |
US20070038516A1 (en) * | 2005-08-13 | 2007-02-15 | Jeff Apple | Systems, methods, and computer program products for enabling an advertiser to measure user viewing of and response to an advertisement |
US20090164253A1 (en) * | 2005-10-27 | 2009-06-25 | Hugh Lyshkow | Use of Mobile Communications Device to Direct Medical Workflow and as a Repository of Medical information |
EP1968691A4 (en) * | 2005-12-14 | 2012-01-25 | Welch Allyn Inc | Medical device wireless adapter |
PL3487155T3 (en) | 2005-12-15 | 2022-01-03 | Nokia Technologies Oy | Method, device and computer program product for network-based remote control over contactless secure storages |
EP1960974A4 (en) | 2005-12-16 | 2010-07-28 | Nokia Corp | Method and device for controlling and providing indications of communication events |
WO2007120904A2 (en) * | 2006-04-14 | 2007-10-25 | Fuzzmed, Inc. | System, method, and device for personal medical care, intelligent analysis, and diagnosis |
US7623486B2 (en) * | 2006-06-30 | 2009-11-24 | T-Mobile Usa, Inc. | System and method for connecting to a voice network, such as wirelessly connecting to a UMA network |
US8523069B2 (en) | 2006-09-28 | 2013-09-03 | Visa U.S.A. Inc. | Mobile transit fare payment |
US8566239B2 (en) | 2007-02-22 | 2013-10-22 | First Data Corporation | Mobile commerce systems and methods |
US8926509B2 (en) * | 2007-08-24 | 2015-01-06 | Hmicro, Inc. | Wireless physiological sensor patches and systems |
TW201021759A (en) * | 2008-12-12 | 2010-06-16 | Hmd Biomedical Inc | Integrated system for transmitting medical measurements through infrared rays |
US20110167133A1 (en) * | 2010-01-05 | 2011-07-07 | Jain Praduman D | System, method, and device for medical device data capture and processing |
US10453157B2 (en) * | 2010-01-22 | 2019-10-22 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US8965274B2 (en) * | 2012-07-16 | 2015-02-24 | Verizon Patent And Licensing Inc. | Session continuity in wireless local area networks with internet protocol level mobility |
US10021087B2 (en) * | 2014-09-15 | 2018-07-10 | Mansour Aaron Karimzadeh | Method and system for providing a secure communication channel to portable privatized data |
-
2013
- 2013-11-12 US US14/078,440 patent/US10892044B2/en active Active
-
2021
- 2021-01-06 US US17/142,975 patent/US11769574B2/en active Active
-
2023
- 2023-09-25 US US18/372,550 patent/US20240038345A1/en active Pending
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109102853A (en) * | 2018-08-30 | 2018-12-28 | 武汉携康智能健康设备有限公司 | A kind of health management system arranged and method based on Internet of Things and cloud computing |
Also Published As
Publication number | Publication date |
---|---|
US10892044B2 (en) | 2021-01-12 |
US20240038345A1 (en) | 2024-02-01 |
US11769574B2 (en) | 2023-09-26 |
US20210174918A1 (en) | 2021-06-10 |
US20150134358A1 (en) | 2015-05-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11769574B2 (en) | Transmitting medical digital artifacts to a mobile device | |
US20180130548A1 (en) | Using an NFC Enabled Mobile Device To Manage Digital Medical Artifacts | |
US20210174325A1 (en) | Nfc mobile payments using tokenization | |
KR102549451B1 (en) | Patient-facing mobile technology that helps physicians achieve quality measures for value-based payment | |
US9317846B2 (en) | Point of sale for mobile transactions | |
US9443276B2 (en) | Event-based asset tracking, order adherence, and rewards management with NFC-enabled electronic devices | |
AU2008265667B2 (en) | Health information services using phone | |
US20110021140A1 (en) | Method and apparatus for providing home healthcare services using a sensor network | |
US20150381793A1 (en) | Bracelet with buttons remotely connected to a smart phone information accessing system | |
KR20170127854A (en) | Electronic apparatus providing electronic payment and operating method thereof | |
CN106485486A (en) | The method for processing payment information of electronic equipment and device | |
US20100102123A1 (en) | Systems, Methods, and Apparatus for Facilitating Access to Medical Information | |
US20220310217A1 (en) | System and method for generating a comprehensive individualized electronic health information monetization platform | |
US20150106118A1 (en) | Cloud-Based Storage and Retrieval of Medical Information Using Near Field Communication Devices | |
CN107203878B (en) | Payment transaction method and electronic equipment thereof | |
US20160188840A1 (en) | Proper dispensing of items through proximity detected devices with users | |
JP2011039674A (en) | Medical database center system | |
Patil et al. | NFC based health monitoring and controlling system | |
AU2012207300B2 (en) | Event-Based Asset Tracking with NFCEnabled Electronic Devices | |
US20140122118A1 (en) | Personal medical information storage device and system | |
Razmi et al. | The use of NFC technology to record medical information in order to improve the quality of medical and treatment services | |
KR20180090693A (en) | Electronic device and method for performing a plurality of payments | |
KR20180091257A (en) | Electronic device and method for payment using the same | |
Devendran et al. | Mobile healthcare system using NFC technology | |
Devendran et al. | Mobile Healthcare–Proposed NFC Architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FISHER, MICHELLE, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLAZE MOBILE, INC;REEL/FRAME:033046/0880 Effective date: 20140606 |
|
FEPP | Fee payment procedure |
Free format text: PETITION RELATED TO MAINTENANCE FEES GRANTED (ORIGINAL EVENT CODE: PTGR); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER |
|
STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 4 |