Method and system for generating and validating clinical reports with built-in automated measurement and decision support

• US 20070112599A1
• Filed: 10/24/2006
• Published: 05/17/2007
• Est. Priority Date: 10/26/2005
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Original Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Inventors: Haider, Sultan, Comaniciu, Dorin, Chakraborty, Amit, Mukherjee, Saikat, Dickmann, Christoph, Palanivelu, Sridharan, Liu, Peiya, Wetekam, Volker, Scholl, Stefan, Vaupel, Jurgen
• Application Number:
  US11/585,471
• Publication Number:
  US 20070112599A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof

Abstract

A method and system for generation and validation of clinical reports with built-in automated measurement and decision support is provided. XML templates may be used for ensuring report data quality. The template data may include static, dynamic, calculated data, and others. The validation method may be based on formal logical constraint specifications. The constraint descriptions may include data types, cardinality, order, co-occurrence, Boolean logic, read-only data, regular expression patterns, etc. The method can be used to validate collected data on-the-fly based on constraint specifications without human interaction.

Claims

1. A method for generating and validating a clinical report, comprising:

collecting data;

interpreting automated measurements and decision support data within one or more template based collection forms;

interpreting one or more logical constraint specifications described by a formal specification language within the one or more template based collection forms;

validating the collected data as it is collected by comparing the collected data against the interpreted logical constraint specifications;

generating a warning condition when data cannot be validated against the interpreted data constraint rules;

continuing to collect data when data is successfully validated against the interpreted data constraint rules; and

generating a validated report comprising the collected and validated data based on a template provided within the template based collection forms.

2. The method of claim 1, wherein the template based collection forms comprise:

a PDF file base layer comprising a template for generating a validated clinical report; and

an overlay for specifying the logical constraint specifications on form fields.

3. The method of claim 1, wherein the collected data is defined in XML syntax.

4. The method of claim 1, wherein the formal specification language for describing the logical constraint specifications is Template Data Constraint Language (TDCL).

5. The method of claim 1, wherein each of the logical constraint specifications is described in terms of:

selectnodes for specifying affected context variables and fields;

content for expressing logical constraints under the context of current selectnodes;

attributes for expressing logical constraints under the context of current selectnodes; and

condition for specify a Boolean expression of logical variables.

6. The method of claim 5, wherein the selectnodes comprise the following properties:

Xpath for describing the context of the selected fields in data collection forms based on the standard XML addressing mechanism;

FieldNames for alternatively describing selected field context by using field name conventions;

ContentVar for declaring a content variable of current selected XPath content;

AttributeVars for declaring attribute variables of current selected XPath content; and

Protection for declaring current protection mode for selectnodes.

7. The method of claim 5 wherein the content and attribute elements comprise the following properties to specify the combination of desired constraints:

StringExp for specifying a string type;

TypeExp for describing a data type;

CardinalExp for declaring a content variable for current selected XPath content;

ArithExp for declaring attribute variables for current selected XPath content;

Formula for declaring attribute variables for automated calculation formula of current selected XPath content;

MeasureVar for declaring an automated measurement variable name for each Content or Attribute constraint element;

DecisionVar for declaring an automated decision support variable name for each Content or Attribute constraint element; and

LogicVar for declaring a logical variable name for each Content or Attribute constraint element.

8. The method of claim 5, wherein the condition for specify a Boolean expression of logical variables comprises the following properties:

premise for expressing a logical premise;

require for expressing a logical “

and”

; and

except for expressing a logical “

not”

.

9. A system for generating and validating a clinical report, comprising:

a data collector for receiving data, interpreting automated measurements and decision support data, and interpreting one or more logical constraint specifications described by a formal specification language;

a data validator for validating the collected data as it is collected by comparing the collected data against the interpreted logical constraint specifications; and

template based collection forms for providing the one or more logical constrain specifications and for providing a template for the generated report.

10. The system of claim 9, wherein the template based collection forms comprise:

a PDF file base layer comprising a template for generating a validated clinical report; and

an overlay for specifying the logical constraint specifications on form fields.

11. The system of claim 9, wherein the collected data is defined in XML syntax.

12. The system of claim 9, wherein the formal specification language for describing the logical constraint specifications is Template Data Constraint Language (TDCL).

13. The system of claim 9, wherein each of the logical constraint specifications is described in terms of:

selectnodes for specifying affected context variables and fields;

content for expressing logical constraints under the context of current selectnodes;

attributes for expressing logical constraints under the context of current selectnodes; and

condition for specify a Boolean expression of logical variables.

14. The system of claim 13, wherein the selectnodes comprise the following properties:

Xpath for describing a context of the selected fields in data collection forms based on the standard XML addressing mechanism;

FieldNames for alternatively describing selected field context by using field name conventions;

ContentVar for declaring a content variable of current selected XPath content;

AttributeVars for declaring attribute variables of current selected XPath content; and

Protection for declaring current protection mode for selectnodes.

15. The system of claim 13, wherein the content and attribute elements comprise the following properties to specify the combination of desired constraints:

StringExp for specifying a string type;

TypeExp for describing a data type;

CardinalExp for declaring a content variable for current selected XPath content;

ArithExp for declaring attribute variables for current selected XPath content;

Formula for declaring attribute variables for automated calculation formula of current selected XPath content;

MeasureVar for declaring an automated measurement variable name for each Content or Attribute constraint element;

DecisionVar for declaring an automated decision support variable name for each Content or Attribute constraint element; and

LogicVar for declaring a logical variable name for each Content or Attribute constraint element.

16. The system of claim 13, wherein the condition for specify a Boolean expression of logical variables comprises the following properties:

premise for expressing a logical premise;

require for expressing a logical “

and”

; and

except for expressing a logical “

not”

.

17. A computer system comprising:

a processor; and

a program storage device readable by the computer system, embodying a program of instructions executable by the processor to perform method steps for generating and validating a clinical report, the method comprising;

collecting data;

interpreting automated measurements and decision support data within one or more template based collection forms;

interpreting one or more logical constraint specifications described by a formal specification language within the one or more template based collection forms;

validating the collected data as it is collected by comparing the collected data against the interpreted logical constraint specifications;

generating a warning condition when data cannot be validated against the interpreted data constraint rules;

continuing to collect data when data is successfully validated against the interpreted data constraint rules; and

generating a validated report comprising the collected and validated data based on a template provided within the template based collection forms.

18. The computer system of claim 17, wherein the template based collection forms comprise:

a PDF file base layer comprising a template for generating a validated report; and

an overlay for specifying the logical constraint specifications on form fields.

19. The computer system of claim 17, wherein the collected data is defined in XML syntax.

20. The computer system of claim 17, wherein the formal specification language for describing the logical constraint specifications is Template Data Constraint Language (TDCL).

21. The computer system of claim 17, wherein each of the logical constraint specifications is described in terms of:

selectnodes for specifying affected context variables and fields;

content for expressing logical constraints under the context of current selectnodes;

attributes for expressing logical constraints under the context of current selectnodes; and

condition for specify a Boolean expression of logical variables.

22. The computer system of claim 21, wherein the selectnodes comprise the following properties:

Xpath for describing a context of the selected fields in data collection forms based on the standard XML addressing mechanism;

FieldNames for alternatively describing selected field context by using field name conventions;

ContentVar for declaring a content variable of current selected XPath content;

AttributeVars for declaring attribute variables of current selected XPath content; and

Protection for declaring a current protection mode for selectnodes.

23. The computer system of claim 21, wherein the content and attribute elements comprise the following properties to specify the combination of desired constraints:

StringExp for specifying a string type;

TypeExp for describing a data type;

CardinalExp for declaring a content variable for current selected XPath content;

ArithExp for declaring attribute variables for current selected XPath content;

Formula for declaring attribute variables for automated calculation formula of current selected XPath content;

MeasureVar for declaring an automated measurement variable name for each Content or Attribute constraint element;

DecisionVar for declaring an automated decision support variable name for each Content or Attribute constraint element; and

LogicVar for declaring a logical variable name for each Content or Attribute constraint element.

24. The computer system of claim 21, wherein the condition for specify a Boolean expression of logical variables comprises the following properties:

premise for expressing a logical premise;

require for expressing a logical “

and”

; and

except for expressing a logical “

not”

.