IP Library Granted Patent US 10,574,606
Granted Patent B2
US 10,574,606 · App. 15/639,684 · Granted Feb 25, 2020

Interoperable clinical document-exchange system

Inventor: Therasa Bell (Boise, ID)
Assignee: KNO2 LLC
H04L51/066H04L51/22
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,574,606
App. No.
15/639,684
Granted
Feb 25, 2020
Kind
B2
Abstract

A method of exchanging messages between users over a network includes receiving a registration request from an organization and provisioning an organizational sub-domain, verifying the registration request according to requirements of a first protocol and provisioning a first user address that is part of the organizational sub-domain, and sending a message from the first user address to a second user address according to the first protocol.

Claims (75)

1. A method for exchanging data over a network, the method comprising the following operations performed by a processor:

receiving a request from an organization having a first user;

provisioning an organizational sub-domain;

verifying the request according to requirements of a first protocol;

provisioning a first user address to the first user wherein the user address is part of the organizational sub-domain;

encrypting a message from the first user address using an encryption message requirement of at least one of symmetric key encryption with a key length, a message syntax, a message length, or a document structure; and

sending the message from the first user address to a second user address according to the first protocol.

2. The method of claim 1 , further comprising:

selecting the first protocol based on a location of the first user in the organization.

3. The method of claim 1 , further comprising verifying the identity of the first user.

4. The method of claim 1 , further comprising providing a list of protocols for sending the message.

5. The method of claim 4 , wherein the protocols in the list of protocols reflect at least one of:

a location of the organization;

a region;

a location of the first user; and

a location of the second user.

6. The method of claim 1 , further comprising:

determining a type of transaction associated with the message;

formatting the message based on the type of transaction;

providing a message field to the first user based on the type of transaction;

selecting the first protocol for sending the message based on the type of transaction; and

sending the message using the first protocol.

7. The method of claim 6 , further comprising:

filling the message fields based on a second transaction associated with the message.

8. The method of claim 1 , wherein encrypting the message includes asymmetric cryptography using a recipient's public key.

9. A system for exchanging data over a network, the system comprising:

a storage device configured to store instructions;

a processor configured to execute the following instructions:

receive a request from an organization having a first user;

provision an organizational sub-domain;

verify the request according to requirements of a first protocol;

provision a first user address to the first user wherein the user address is part of the organizational sub-domain;

encrypt a message from the first user address using an encryption message requirement of at least one of symmetric key encryption with a key length, a message syntax, a message length, or a document structure; and

send the message from the first user address to a second user address according to the first protocol.

10. The system of claim 9 , wherein the instructions are further configured to cause the processor to:

select the first protocol from among at least a second protocol and a third protocol based on a location of the first user in the organization.

11. The system of claim 9 , wherein the instructions are further configured to cause the processor to:

provide a list of protocols for sending the message.

12. The system of claim 11 , wherein the contents of the list of protocols reflect at least one of:

a location of the organization;

a region;

a location of the first user; and

a location of the second user.

13. The system of claim 9 , wherein the instructions are further configured to cause the processor to:

determine a type of transaction associated with the message;

format the message based on the type of transaction;

provide one or more message fields to the first user based on the type of transaction, the message fields comprising required fields and/or optional fields;

select the first protocol for sending the message based on the type of transaction; and

send the message using the first protocol after the required fields are filled out.

14. The system of claim 9 , wherein the instructions are further configured to cause the processor to:

pre-fill one or more of the message fields based on a second transaction associated with the message.

15. The method of claim 9 , wherein encrypting the message includes asymmetric cryptography using a recipient's public key.

16. A non-transitory computer-readable medium storing instructions, the instructions configured to cause a processor to perform operations comprising:

receiving a request from an organization having a first user;

provisioning an organizational sub-domain;

verifying the request according to requirements of a first protocol;

provisioning a first user address to the first user wherein the user address is part of the organizational sub-domain;

encrypting a message from the first user address using an encryption message requirement of at least one of symmetric key encryption with a key length, a message syntax, a message length, or a document structure; and

sending the message from the first user address to a second user address according to the first protocol.

17. The computer-readable medium of claim 16 , wherein the instructions are configured to cause the processor to perform operations further comprising:

selecting the first protocol from among at least a second protocol and a third protocol based on a location of the first user in the organization.

18. The computer-readable medium of claim 17 , wherein the instructions are configured to cause the processor to perform operations further comprising providing a list of protocols for sending the message.

19. The computer-readable medium of claim 18 , wherein the contents of the list of protocols reflect at least one of:

a location of the organization;

a region;

a location of the first user; and

a location of the second user.

20. The computer-readable medium of claim 17 , wherein the instructions are configured to cause the processor to perform operations further comprising:

determining a type of transaction associated with the message;

formatting the message based on the type of transaction;

providing one or more message fields to the first user based on the type of transaction, the message fields comprising required fields and/or optional fields;

selecting the first protocol for sending the message based on the type of transaction; and

sending the message using the first protocol after the required fields are filled out.

21. The computer-readable medium of claim 20 , wherein the instructions are configured to cause the processor to perform operations further comprising pre-filling one or more of the message fields based on a second transaction associated with the message.

22. The method of claim 16 , wherein encrypting the message includes asymmetric cryptography using a recipient's public key.

Assignments (4)
SECURITY INTEREST Recorded Jun 18, 2026
From: KNO2 LLC
To: FIFTH THIRD BANK, N.A., SUCCESSOR IN INTEREST TO COMERICA BANK
Reel/Frame 075003/0255 →
SECURITY INTEREST Recorded Jul 31, 2025
From: KNO2 LLC
To: COMERICA BANK
Reel/Frame 071898/0570 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 6, 2021
From: BELL, THERASA
To: INOFILE LLC
Reel/Frame 056766/0252 →
CHANGE OF NAME Recorded Jul 6, 2021
From: INOFILE, LLC
To: KNO2 LLC
Reel/Frame 056770/0695 →
Continuity (2)
Continuation 14614368 · Feb 4, 2015
Related Publication 20170310618A1 · Oct 26, 2017
Cited By (2)
US 12,205,688 US 12,411,978