Method and apparatus generating and applying security labels to sensitive data

• US 9,800,582 B2
• Filed: 06/02/2014
• Issued: 10/24/2017
• Est. Priority Date: 06/04/2013
• Status: Active Grant

• Current Assignee: Edmond Scientific Co.
• Original Assignee: Edmond Scientific Co.
• Inventors: Decouteau, Duane, Pitale, John
• Primary Examiner(s): HENNING, MATTHEW T
• Application Number:
  US14/293,651
• Publication Number:
  US 20150020213A1
• Time in Patent Office: 1,240 Days
• Field of Search: 726 27
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

The disclosure comprises a method, an apparatus, and instructions for controlling a computer to implement a security labeling service (SLS) to tag an electronic record or data stream with security labels to ensure compliance with access restriction requirements. The SLS tags a record or data stream with security labels according to constraints including jurisdictional (government regulation), organizational policy, and authorization of a subject of record (e.g. patient consent). The SLS consumes a vocabulary dictionary to interpret the record and the constraints to generate rules for tagging the data. The original record or data stream is then tagged according to the rules. The tagged output is used to ensure compliance with the security labels.

Claims

1. A method comprising:

by at least one hardware computer;

receiving, at runtime, a request for an electronic record or electronic data stream from a receiving party;

receiving the electronic record or electronic data stream from at least one repository in response to the received request;

dynamically generating, at runtime, a security label according to the electronic record or electronic data stream, information included in the received request, a subject of record authorization, an organizational policy, and a government regulation, the security label corresponding to at least one item included in the received electronic record or electronic data stream and indicating one or a combination of redaction, restriction, and encryption of at least one item included in the received electronic record or electronic data stream;

inserting, at runtime, the dynamically generated security label into the received electronic record or electronic data stream to generate a tagged electronic record or electronic data stream including the security label and the at least one item corresponding to the security label, thereby enabling automated compliance and enforcement of data handling for each of the subject of record authorization, the organizational policy, and the government regulation according to the information included in the received request, and

outputting the tagged electronic record or electronic data stream with the inserted security label and the at least one item corresponding to the inserted security label.

2. The method according to claim 1, wherein:

the security label corresponds to a HL7 Healthcare Classification System (HCS) standard by a Security Labeling System (SLS); and

the received electronic record or electronic data stream conforms to an HL7 standard that includes Fast Healthcare Interoperability Resources (FHIR) implementations.

3. The method according to claim 2, further comprising:

by the at least one computer;

determining whether the receiving party ensures proper compliance with access restrictions according to the HL7 HCS security label and the organizational policy;

transmitting the tagged electronic record or electronic data stream upon determining that the receiving party ensures proper compliance with the access restrictions; and

redacting the tagged electronic record or electronic data stream according to the security label and organizational policy upon determining the receiving party does not ensure proper compliance with the access restrictions, and transmitting the redacted tagged electronic record or electronic data stream.

4. The method according to claim 1, further comprising:

by the at least one computer;

determining whether the receiving party ensures proper compliance with access restrictions according to the security label and the organizational policy;

transmitting the tagged electronic record or electronic data stream to the receiving party upon determining the receiving party ensures proper compliance with the access restrictions; and

redacting the tagged electronic record or electronic data stream according to the security label and organizational policy upon determining the receiving party does not ensure proper compliance with the access restrictions, and transmitting the redacted tagged electronic record or electronic data stream.

5. A method according to claim 1, wherein the received electronic record or electronic data stream is a medical record.

6. A method according to claim 1, wherein the received electronic record or electronic data stream is a record that contains sensitive or classified information.

7. A method according to claim 1, wherein

the received electronic record or electronic data stream is associated with the subject of record;

and

the inserting further comprises;

determining a rule for tagging the received electronic record or electronic data stream based on each of the electronic record or electronic data stream, the information included in the received request, the subject of record authorization, the organizational policy, and the government regulation;

decomposing the received electronic record or electronic data stream into a decomposed data source including the at least one item; and

generating at least one directive based on a correspondence between the at least one item included in the decomposed data source and the rule for tagging, the at least one directive indicating transformation of the rule for tagging into the security label and indicating the security label is to be inserted into the received electronic record or electronic data stream at a location corresponding to the at least one item; and

determining an output mode for the outputting of the tagged electronic record or electronic data stream;

wherein the output mode is one or a combination of storing and transmitting.

8. A method according to claim 7, wherein

the subject of record is a medical patient;

the received electronic record or electronic data stream is a medical record; and

the organizational policy is provided by a health service provider, Health Insurance Portability and Accountability Act (HIPAA) covered entity or business associate, or a record custodian.

9. A method according to claim 8, wherein:

the determining of a rule for tagging utilizes one or a combination of a vocabulary dictionary and a purpose for requesting the medical record,

the purpose for requesting the medical record is included in the information included in the received request, and

the dynamically generating, at runtime, the security label is further according to the purpose for requesting the medical record.

10. A method according to claim 9, wherein the vocabulary dictionary comprises one or a combination of Snomed-CT, RxNorm, International Statistical Classification of Diseases (ICD), HL7, and HL7 HCS.

11. A method according to claim 8, wherein:

at least one of the subject of record authorization, the organizational policy, and the government regulation is expressed in a rule language, and

the rule language comprises one or a combination of Drool Rule Language (DRL) and RuleML; and

the at least one directive indicates the transformation of the rule from the expression in the rule language into the security label expressed in a format of the received electronic record or electronic data stream.

12. A method according to claim 7, further comprising encrypting, by the at least one hardware computer, the tagged electronic record before transmitting.

13. A non-transitory computer readable storage medium containing instructions for controlling one or more hardware processors to implement the method according to claim 1.

14. A method comprising:

by at least one computer;

receiving, at runtime, a retrieval request to retrieve an electronic record associated with a subject of record;

determining a rule for dynamically tagging, at runtime, the electronic record based on the electronic record, information included in the retrieval request, a vocabulary dictionary, an authorization constraint, an organizational policy constraint, and a government rule constraint, to enable automated compliance and enforcement of data handling;

retrieving the electronic record from a repository according to the retrieval request;

decomposing the electronic record into a decomposed data source;

tagging the electronic record at runtime with a security label corresponding to at least one item in the decomposed data source and according to a correspondence between the determined rule and the at least one item in the decomposed data source by inserting the security label into the electronic record to generate a tagged electronic record including the security label and the at least one item corresponding to the security label, the security label indicating one or a combination of redaction, restriction, and encryption of the at least one item as the compliance and enforcement of the data handling according to the information included in the retrieval request; and

outputting the tagged electronic record with the inserted security label and the at least one item corresponding to the inserted security label;

wherein the authorization constraint is provided by the subject of record.

15. A method according to claim 14, wherein:

the electronic record is in XML or JSON format; and

the outputting the tagged electronic record is transmitted within an XML or JSON stream.

16. A method according to claim 15 wherein:

the subject of record is a medical patient;

the electronic record is a medical record of the medical patient

the repository contains electronic records in HL7 standard common data structures and elements or an HL7 Fast Healthcare Interoperability Resources (FHIR) implementation; and

the compliance and enforcement is in accordance with HL7 Healthcare Classification System (HCS).

17. A method according to claim 15, wherein:

a user within an organization corresponding to the organizational policy constraint sends the retrieval request; and

the organizational policy constraint is provided by the organization.

18. A method according to claim 17, wherein

the organization is a health service provider, and

the determining the rule is further based on a purpose for requesting the electronic record included in the information included in the retrieval request.

19. A method according to claim 17, wherein the vocabulary dictionary comprises one or a combination of Snomed-CT, RxNorm, ICD, and HL7, and HL7 HCS.

20. A method according to claim 15, wherein:

one or a combination of the authorization constraint, the organizational policy constraint, and the government rule constraint is expressed in a rule language,

the rule language comprises one or a combination of Drool Rule Language (DRL) and RuleML,

the rule is transformed from the expression in the rule language to a format of the electronic record and inserted as the security label into the electronic record at a location in the electronic record corresponding to the at least one item in the decomposed data corresponding to the determined rule.

21. A method according to claim 15, further comprising encrypting, by the at least one computer, the tagged electronic record before outputting.

22. A method according to claim 15, further comprising enforcing data security according to the security label by an entity sending the retrieval request.

23. An apparatus comprising:

a memory storing instructions;

at least one hardware processor, wherein upon executing the instructions, the at least one hardware processor implements;

a rule generation service configured to dynamically generate, at runtime, a rule from a vocabulary dictionary, rule constraints, decision considerations included in information included in a runtime request to retrieve an electronic record from an original data source, and the electronic record;

an extraction engine configured to transform the electronic record into a decomposed data source;

a rules engine configured to generate, at runtime, a directive from a correspondence between the rule generated by the rule generation service and at least one item in the decomposed data source, the directive indicating how to transform the rule into a security label corresponding to the at least one item in the decomposed data source and indicating where to insert the security label into the electronic record, and the security label indicating at least one of redaction, restriction, and encryption of the at least one item in the decomposed data source according to the rule constraints and the decision considerations included in the information included in the request to retrieve the electronic record from an original data source; and

a transformation engine configured to output an electronic record tagged with the security label by inserting the security label at runtime into the electronic record according to the directive to enable automated compliance and enforcement of data security according to the rule constraints and the decision considerations included in the information included in the request to retrieve the electronic record from an original data source, the tagged electronic record including the security label and a portion of the electronic record corresponding to the at least one item in the decomposed data source corresponding to the security label.

24. An apparatus according to claim 23, further comprising an encryption engine configured to encrypt the electronic record tagged with the security label.

25. An apparatus according to claim 24, wherein the rule constraints comprise an authorization of a subject of record, an organizational policy, and a government rule.

26. An apparatus according to claim 25, wherein:

the subject of record is a medical patient,

the requested electronic record is a medical record associated with the medical patient originating from a HL7 standard common data structure or an HL7 Fast Healthcare Interoperability Resources (FHIR) implementation as the original data source; and

the compliance and enforcement is in accordance with HL7 Healthcare Classification System (HCS).

27. An apparatus according to claim 26, wherein the vocabulary dictionary comprises one or a combination of Snomed-CT, RxNorm, ICD, and HL7, and HL7 HCS.

28. An apparatus according to claim 23, wherein the decision considerations comprise a purpose for requesting the medical record and a workflow consideration.

29. An apparatus according to claim 27, wherein:

rule constraints are expressed in a rule language,

the rule language comprises one or a combination of Drool Rule Language (DRL) and RuleML, and

the directive indicates transformation of the rule expressed in the rule language into the security label expressed in a format of the original data source.