CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 61/240,174, filed on Sep. 4, 2009, and entitled â€œMethod Of Documenting Patients' Clinical Status Across Multiple Diagnostic Dimensions,â€ the entire content of which is hereby expressly incorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to computer software; and more particularly to a method of documenting patients' clinical status across multiple diagnostic dimensions.

BACKGROUND

To date there is no accepted and widely used method for capturing the clinical data necessary to perform quality-based outcomes measurement in the field of mental health treatment. Consequently, Managed Care Organizations (MCOs) have focused only on measuring utilization metrics (frequency and/or cost of services), which do not reflect efficacy of treatment and a patient's clinical improvement. Two primary factors contribute to this problem. One is the lack of agreement on a standard set of criteria to measure clinical status that is acceptable to all mental health providers across diverse schools of thought. The second is the unavailability of an easy-to-use and comprehensive methodology or technology to rapidly capture relevant clinical information needed to measure a patient's clinical improvement.

Currently, there is a high percentage of concordance between level of case (LOC) guidelines across MCOs. However, the LOC guidelines are only guidelines and are relatively vague with regard to clinical signs and symptoms. The application of LOC guidelines are subjective and depend on clinicians' interpretation of the guidelines to meet medical necessity criteria.

Inter-rater reliability (IRR) regarding the selection of a LOC for a particular case is approximately 70% across clinicians (including case managers and medical directors) in MCOs, hospitals, and provider groups. This occurs because (a) clinicians are selective and subjective about the clinical information captured about a particular case; and (b) clinicians tend to focus on varied aspects of cases based on their respective clinical training and school of thought (e.g., Cognitive Behavioral versus Psychodynamic). Consequently, clinicians do not necessarily consider all aspects of a case, which impacts decision making regarding the status, disposition and LOC of a case.

Given the absence of an acceptable quality-based methodology for measuring patients' clinical improvement, providers are subject to profiling based on traditional utilization management metrics (as defined above). Current standard quality indicators do not include whether a diagnosis selected by a clinician meets Diagnostic and Statistical Manual of Mental Disorders (DSM) criteria, whether providers use evidence-based treatment modalities, or whether treatment outcomes are adjustment for case mix (proportion of complex versus non-complex cases, diagnostic categories, and severity of cases) across providers.

SUMMARY

In some embodiments, the present invention is a computer implemented method for managing a patient's clinical status. The method includes: storing rules in a database; storing clinical domains including a set of clinical variables; storing information about the patient in the database; receiving responses to one or more questions about the patient's status for one or more clinical domains. The method then generates derived variables from the stored information, the stored clinical variable and the responses to one or more questions using one or more of the stored plurality of rules; calculates stratified domain levels for one or more of the plurality of clinical domains from the stored information, the stored clinical variables and the generated derived variables; and calculates a level of care from the stratified domain levels and the generated derived variables.

The method may also calculate a level of urgency from the stratified domain levels and the generated derived variables.

In some embodiments, the present invention is a computer implemented method for managing a patient's clinical status. The method includes: storing rules in a database; storing clinical domains including a set of clinical variables; storing information about the patient in the database; receiving responses to one or more questions about the patient's status for one or more clinical domains. The method then generates derived variables from the stored information, the stored clinical variable and the responses to one or more questions using one or more of the stored plurality of rules; calculates stratified domain levels for one or more of the plurality of clinical domains from the stored information, the stored clinical variables and the generated derived variables; and calculates a level of urgency from the stratified domain levels and the generated derived variables.

The method may also calculate a level of care from the stratified domain levels and the generated derived variables.

The method may also generate a report based on the stored information about the patient and the calculated level of care.

In some embodiments, the present invention is a computer implemented method for managing a patient's clinical status. The method includes: storing a plurality of rules and a plurality of clinical domains in a database, each clinical domain including a set of clinical variables selected based on clinical research to describe clinical acuity and determine risk; defining a plurality of levels of care representing the patient's clinical status; receiving responses to one or more questions about the patient's status for one or more clinical domains; generating derived variables from the responses to one or more questions using one or more of the stored plurality of rules; stratifying a patient's status in each clinical domain to represent a clinical severity level for each clinical domain; joining the clinical severity levels across the plurality of clinical domains with the generated derived variables and the responses; and mapping the clinical severity levels to medical necessity criteria related to each of the plurality of levels of care; and generating a report based on the mapped the clinical severity levels and the levels of care.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary architectural block diagram of a software, according to some embodiments.

FIG. 2 shows a simplified security level block diagram, according to some embodiments of the present invention.

FIG. 3 shows a simplified process flow diagram, according to some embodiments of the present invention.

FIGS. 4A and 4B illustrate exemplary Lethality Domain screens, according to some embodiments of the present invention.

FIGS. 5A-5N depict various exemplary Domain screens, according to some embodiments of the present invention.

FIGS. 6A-6E show various exemplary reporting screens, according to some embodiments of the present invention.

FIGS. 7A and 7B illustrate an abbreviated example of how the four levels of rules work together to generate a recommended Level of Care based on the user's input, according to some embodiments of the present invention.

DETAILED DESCRIPTION

In some embodiments, the present invention is a computer software application, available to providers (including facilities) via a computer network, for example, the Internet, that enables providers to document and/or manage a patient's clinical status (right care at the right Level of Care and Urgency) across multiple diagnostic dimensions and verify diagnoses. The invention has embedded computerized decision processes that suggest a Level of Care and Urgency based on the information from a plurality of clinical domains. The application generates a complete clinical report including a graphical presentation that serves to track patient's progress in treatment (outcomes). Data collected using the invention creates a valuable asset to support research and development, disease management and predictive modeling, and provider profiling.

In some embodiments, the present invention performs three diverse functions in a single application: Level of Care (LOC) determination, outcomes measurement, and provider profiling.

Level of Care determinations are consistent and accurate. A lot of this is due to the user interface that leverages branching logic for rapid data capture, computerized processes that interpret the data, and the fact that the clinical information captured is mapped to standard level of care guidelines. This minimizes subjective interpretative variance. In this capacity, the invention supports disease management for disease-specific states and predictive modeling for recidivism.

The invention also supports provider profiling in a unique way based on quality measures (effectiveness of treatment) rather than utilization metrics (frequency and cost of services). In a reciprocal fashion, the invention provides ongoing training by clarifying the clinical characteristics associated with each level of care, and matching symptom profiles with correct diagnoses.

With respect to LOC decision making, the invention automates the application of LOC guidelines and adds a dimension of specificity regarding clinical signs and symptoms related to any patient condition. The present invention guides the clinician with regard to the information that is collected, and captures information across several clinical domains that are required to provide complete clinical decision-making. The invention then applies complex computerized decision making processes to the information to derive the most appropriate LOC recommendation.

With respect to the â€œOutcomes,â€ in the present invention, they are measurable because the invention captures data from several domains that define a patient's clinical status. Data for each of the several domains is quantifiable individually and in the aggregate. Improvements and decrements are quantifiable within each domain over time and across cases. In addition, data can be aggregated across the domains and quantified to provide a view of the patient's overall functioning, status and disposition. The invention enables clinicians to understand cases at both the individual domain level and, simultaneously, across all domains. This allows clinicians to understand how changes in any individual domain, or combination of domains, effects overall functioning and status.

With respect to the â€œProvider Profiling, Individual Providers and Facilities,â€ the invention supports true provider profiling based on quality indicators instead of traditional utilization management metrics (such as frequency and/or cost of services). In some embodiments, quality indicators measure diagnostic veracity (i.e., diagnostic criteria met or not met), use of evidence-based treatment modalities, and outcomes such as clinical change over time as measured by specific functionality, signs and symptoms. The invention also enables adjustment for case mix (as defined above) across providers.

FIG. 1 is an exemplary architectural block diagram of a software, according to some embodiments. One or more client databases 11 include data related to the patients and other data such as clinical rules, level of care criteria (explained below), domain stratification logic (explained below), etc. Each database may reside on one or more computers. The users use a terminal or a computer, such as a Personal Computer (PC) to access the software of the present invention running on one or more servers, through a computer network, such as the Internet.

A Presentation Layer 14 provides support for the interactions between the actors, or the users of the system, and the software system itself through the presentation of user interfaces. A Business Logic Layer 13 provides support for application specific business processes, as well as, the application and enforcement of business and data integrity rules. A Data Access (Database) Layer 12 provides support for data access and persistence in conjunction with the client databases 11.

With respect to directional dependencies, and based upon the hierarchical structure of the responsibility-based layers design pattern, the Presentation Layer 14 initiates communication with the Business Logic Layer 13 and, occasionally, the Data Access Layer 12. Similarly, the Business Logic Layer initiates communication with the Data Access (Database) Layer 12, which initiates communication with the client databases 11. It is noted that when reference to â€œa database,â€ is made, as one skilled in the art would readily recognize, the database, may be a combination of one or more databases residing on one or more computers that may be connected via a computer network, for example, a distributed database. Each of these layers is comprised of numerous classes.

FIG. 2 shows a simplified security level block diagram, according to some embodiments of the present invention. The security system operates at three levels: master database level, client database level, and record level. In some embodiments, at the client database level, separate databases are used for each licensed facility, hospital, provider group, or managed care company, for example, Client Database A 23 and Client Database B 22, as shown. In some embodiments, for individual users who purchase a monthly user subscription and are not part of a hospital, group, etc., a single aggregate database may be used. Within the aggregate user database, individual providers can access only the records they create; they cannot view any record created by another user, even if the same patient sees more than one provider.

Within a client database (licensed to a facility, hospital, provider group, or managed care company), users may be assigned a security level: High, Medium, or Low. Patient records are also assigned a security level: High, Medium, or Low. Users 26 can access all patient records at or below their own security level via the Internet 25 and through a web application 24 running on one or more server computers. For example, a user with a Medium security level can view on her terminal display all patient records with a security level of Medium or Low.

A Master Database 21 is used above the individual client databases and the aggregate user database to manage login credentials for each user, and the association between the user and one client database or the aggregate user database. In some embodiments, each user login is associated with only one database.

In some embodiments, users login to a Web application according to the invention through the Internet. Login credentials for each user are stored in the Master database 21. Once a user's credentials are verified in the Master database 21, the software application of the present invention links the user to their corresponding database. For example, as illustrated in FIG. 2, when User A logs in to the application 24, his credentials are verified in the Master database 21. Upon verification, the user's session is directed to Client Database A 23.

FIG. 3 shows a simplified process flow diagram, according to some embodiments of the present invention. In some embodiments, the variable mapping and decision logic (rules) are accomplished on four separate levels and combined in a single application. Individual item responses record users' input and support user interface screen controls to speed data input, in level 1. Derived variables are generated from combinations of individual item responses using computational process, rules and Boolean logic, in level 2. In level 3, severity scores are generated for each of the seven domains, from 1 (lowest severity) through 4 (highest severity), based on derived variables and individual item responses. Finally, in level 4, Level of Care (LOC) decisions are based on combinations of domain severity scores, derived variables, and individual item responses.

As shown, the user (for example, a managed care personnel) logs in and opens a patient's record, in block 31. In block 32, the user enters patient's clinical information. Some examples of patient's clinical information is depicted in FIG. 4A and described below. The one or more databases then stores the patient's information, for example, as raw data (block 33). The invention then uses the stored patient's information to calculate derived variables, in block 34. The derived variables are generated from combinations of individual item responses using computational processes, rules and Boolean logic. The invention then uses the stored patient's information and the derived variables to calculate stratified domain levels and domain scores (described in detail below), in block 35. In block 36, invention uses the stored patient's information, the derived variables, and the calculated domain levels to calculate (recommend) LOC and/or level of urgency. Finally, the invention generates a report including narratives, based on the patient's information, diagnoses and symptoms recommended LOC and/or level of urgency, in block 37. FIGS. 5D through 5H illustrate how Diagnoses and Symptoms related to a particular Diagnosis is gathered.

In some embodiments, the derived variables in the calculated domain levels determine the domain scores, as each item/variable has a score. The domain scores are used to track outcomes, identify high risk patients in a disease state (disease management) and for predictive modeling).

In some embodiments, the clinical logic begins by defining wellness and illness as a continuum in any given population. The assumption is that everybody moves from wellness to a state of illness and perhaps back and forth between wellness and illness. Hence, the wellness and illness is a continuum. Further, an individual person's health status is defined and recorded using, for example, seven domains, each having a display screen for entering, displaying and editing the data.

1. Symptom Severity

2. Lethality

3. Psychosocial Support

4. Functional Impairment

5. Medical Co-morbidity

6. Patient Resources

7. Provider Resources

Each domain has a specific set of clinical variables. These variables are selected on the basis of community standards and clinical research as being the most relevant to describe clinical acuity (highest to lowest), and determine risk (greatest to least) for morbidity/illness or wellness. The format, wording and order of the variables are designed, tested, and refined to maximize speed of data input, and make the software application as intuitive as possible regardless of users' clinical orientation.

In other words, the invention stores rules, clinical domains including a set of clinical variables, and information about the patient in one or more databases. The invention then receives responses to one or more questions about the patient's status for one or more clinical domains, utilizing, for example graphical user interfaces (GUIs). The invention then generates derived variables from the stored information, the stored clinical variable and the responses to one or more questions using one or more of the stored plurality of rules, calculates stratified domain levels for one or more of the plurality of clinical domains from the stored information, the stored clinical variables and the generated derived variables; and calculates a level of care and or a level of urgency from the stratified domain levels and the generated derived variables. A report may also be generated providing the calculated information to the users in an effective way.

In some embodiments, embedded in each domain screen is a screen control logic that guides users through the questions based on their responses to previous items. The branching logic disables questions that are not necessary or clinically inconsistent with users' answers on previous questions within and across domains; users simply skip the disabled items. Similarly, within questions, the branching logic enables â€œchildâ€ options based on users' responses to â€œparentâ€ options, thereby visually guiding users through predetermined logic paths encoded within the questions.

FIGS. 4A and 4B illustrate exemplary Lethality Domain screens, according to some embodiments of the present invention. As an example, when the Lethality domain screen (shown in FIG. 4A) first appears, the check boxes labeled â€œDanger to Selfâ€ , â€œDanger to Othersâ€ , and â€œGravely Disabledâ€ are all disabled. Only when the user selects either a button labeled â€œa clear potential for lethality manifested byâ€ or a button labeled â€œpotential for lethality,â€ the check boxes are enabled for the user to select â€œDanger to Selfâ€ , â€œDanger to Othersâ€ , and/or â€œGravely Disabledâ€ . If the user selects â€œDanger to Selfâ€ but not â€œDanger to Othersâ€ , the user interface disables questions related to danger to others but, it enables all items related to danger to self such as ideations with plans, available means, lethality of means, impulsivity and hopelessness.

For example, in the Lethality screen, the item in question 1 is marked positive, meaning that the patient has a clear presence of lethality manifest by Danger to Self Subsequent questions, for example questions 2, provide choices about the seriousness of the suicidal ideation, question 4 and 5 about the viability of means to follow through on a suicidal plan and asks if the means are by lethal or non-lethal means, and questions 7 and 8 are associated risk factors for somebody potentially following through and making such an attempt.

Then, if the user indicates that the patient has â€œpassive suicidal ideationsâ€ instead of â€œsuicidal ideations with plansâ€ , items related to availability and lethality of means disable because they are clinically inconsistent with passive suicidal ideation, as shown in FIG. 4B.

A second level of logic is a set of derived variables that are generated from combinations of individual item responses using computational processes, rules and Boolean logic. Derived variables include:

- a) number of Axis I and Axis II diagnoses by verification status by severity level;
- b) risk for lethality based on impulsivity, depression, command hallucinations, manic state, paranoid delusions, and intoxication;
- c) risk for lethality plus past history of engaging in behavior to harm self or others plus whether the patient's social environment can provide protection against harmful behaviors;
- d) the degree of risk in the home as a function of drugs, violence, abuse, and neglect; and
- e) number of blank and non-blank domains.

These variables are used in support of higher levels of decision logic.

A third level of logic is the stratification of the patient's status in each domain. Individual variables and derived variables are joined in a series of Boolean processes (â€œandâ€ statements, â€œorâ€ statements, etc.) to represent all possible combinations of responses that represent clinical severity at one of, for example, four levels of severity. Individual or clinical variables are each of the data elements which are clinical in nature, and displayed in each of the multiple questions shown in each page/domain/screen. Derived variables are when the invention clusters the individual variables in some clinical sets or groupings that allow us to stratify the groups into four levels of clinical severity and provide a â€œderived valueâ€ . Inconsistent combinations of items are prevented by the screen logic (that is upon users attempt), which reduces the total possible number of combinations.

As an example, stratification of responses in the Lethality Domain, labeled â€œLâ€ , generates scores labeled â€œL4â€ , â€œL3â€ , â€œL2â€ , and â€œL1â€ , with L4 being those with the most severe clinical presentation and risk, and L1 being those with the mildest symptoms and risk. Stratification is performed across the first five domains as follows:

- Domain 1, Symptom Severity or â€œSâ€ is stratified as S4, S3, S2 and S1, with S4 as the most severe and S1 as the least severe.
- Domain 2, Lethality or â€œLâ€ is stratified as L4, L3, L2 and L1, with L4 as the most severe and L1 as the least severe.
- Domain 3, Psychosocial or â€œPâ€ is stratified as P4, P3, P2 and P1, with P4 as the most severe and P1 as the least severe.
- Domain 4, Functional Impairment or â€œFâ€ is stratified as F4, F3, F2, and F1, with F4 as the most severe and F1 as the least severe.
- Domain 5, Medical Conditions or â€œMâ€ is stratified as M4, M3, M2, and M1, with M4 as the most severe and M1 as the least severe.

In this example, Domains 6 and 7, Patient Resources and Provider Resources, respectively, are not stratified, however, may be stratified upon the need, as described above.

Examples of criteria used to map responses in each domain to the stratification levels are presented in Appendix A in a table format, the entire contents of which are hereby expressly incorporated by reference. The criteria presented in Appendix A are the â€œanchorâ€ criteria, representing the clearest examples of the response sets for each stratification level. Because users can enter many other combinations of responses, including leaving items unanswered, a set of â€œgapâ€ equations (criteria) is created to account for all combinations of input responses (excluding those prevented by the screen logic). Each gap equation is mapped to a stratification level based on the degree to which it deviated from its nearest anchor criteria.

A fourth level of logic joins the domain severity levels across the seven domains, with some derived variables and input variables, and maps them to the medical necessity criteria related to each LOC.

In some embodiments, some standard behavioral health level of care categories used in the invention include:

Inpatient

Residential Treatment Program

Partial Hospital Program

Intensive Outpatient Program (IOP)

Outpatient Services

In some embodiments, a separate set of LOC decision logic is used for cases having a substance abuse diagnosis, or dual diagnosis with the focus of treatment being substance abuse. In these cases, an additional level of care labeled â€œSAâ€”Inpatient Medicalâ€ is also used. The substance abuse LOC decision logic employs the same methodology as described above, but the criteria for mapping response sets to the levels of care include American Society of Addiction Medicine (ASAM) criteria for substance abuse.

An exemplary criteria used to map the stratified variables across the different domains to levels of care for substance abuse cases are presented in Appendix B, the entire contents of which are hereby expressly incorporated by reference. In some embodiments, all combinations of domain stratification levels and variables (response sets) are mapped to a level of care. As with the gap equations described above, in some cases mapping of response sets to a level of care is based on the distance between the response set and its closest anchor response set, or it was based on clinical community standards.

The level of care decision logic is capable of handling missing data, that is, the logic checks to see how many and which domain pages are left blank. In some embodiments, a minimum threshold of required information was established as follows based on clinical community standards: Users should provide input for at least one item on the Lethality domain (which will provide some indication of the patient's level of risk) plus at least one item on at least one other domain from Symptom Severity, PsychoSocial Support, Functional Impairment, or Medical Conditions. If only this minimum amount of information is provided, it will result in an outpatient level of care. Additional information is required to document the need for a higher level of care. However, if the user does not provide the minimum amount of information, the invention returns a level of care of â€œInsufficient Inputâ€ .

The invention may also generate a recommended level of urgency for each record. This decision process also uses the domain severity levels, derived variables and input variables, and maps combinations of value to the following levels of urgency:

Emergent: services needed emergently

Urgent: services required urgently

Routine: Services that may be rendered in a routine manner and time frame

Examples of criteria used to map the stratified variables across the different domains to levels of care are presented in Appendix C.

The invention generates an output report that includes the recommended (mapped) level for care and level of urgency. The report includes the rationale, which is a narrative of the input variables within each domain, diagnosis, symptoms, and diagnosis verification. Each domain is given (assigned) a numerical score based on the items selected within the domain. The scores are computed by summing the scores for the component item responses within each domain, based on community standards and research as to the clinical relevance and level of severity of each variable and response within the domain.

In some embodiments, the invention also generates a graph of the domain scores as a visual presentation of the patient's clinical profile. The profile enables users to quickly and clearly see the severity of each domain and its relative value compared to the other domains. After the second, third, and subsequent sessions are completed, the profile displays the domain scores from the current and previous two sessions, enabling users to see changes in the scores individually and globally over time. This serves as an outcome measure of treatment response.

Following the graph, the invention report presents the DSM-IV diagnoses on Axes I, II, and III entered by the user in the Symptom Severity domain; the symptoms associated with the primary diagnosis as selected by the user; and the invention determination of whether the diagnosis was verified by the symptoms selected by the user. Clinical logic is embedded in the application to determine if the symptoms selected by the user meet the DSM IV criteria for the diagnosis, or are suggestive of the diagnosis by meeting a certain percentage (for example, 70%) of the criteria, or do not meet the criteria. The logic is based on clinically accepted community standards.

The diagnosis verification feature of the invention enables clinical managers to profile providers as to their diagnostic integrity and accuracy. This is a critical component of the application as effective treatment and evidence-based medicine requires accurate diagnosis.

In some embodiments, the invention includes several Graphical User Interface (GUI) screens for the user to interact with the invention. Although, for simplification and illustration purposes, specific and at time, detail exemplary screens for the GUIs are described below, the invention is not limited to such screens. Other screens/GUIs may be used with the present invention to input the appropriate data and display desired result.

In some embodiments, users access the invention's software application through a web browser on an Internet-enabled computer via a login screen. On the login screen, they enter their user names and passwords. The system verifies that they are registered users, identifies the database on which they are registered, and opens the application to the Patient Manager window, as depicted in FIG. 5A.

A Patient Manager window enables users to search for individual patient records, and enter new patients. When creating a new patient, users first conduct a search for the patient to avoid creating a duplicate record. To do this, users enter the new patient's name and other available information (e.g., phone number, birth date, Social Security Number) into the Search criteria and click on Search. If the patient does not already exist in the database, the system will display a message asking if the user wants to create a new record. If the user clicks â€œYesâ€ , the system opens the Add/Edit Patient window, as shown in FIG. 5B, and transfers into it the information used for the search.

To create the new patients, users complete the information in an Add/Edit Patient dialog window and click Save, as depicted on the right side of FIG. 5B. The system returns to the Patient Manager window with the new patient record in focus/highlighted as shown in FIG. 5C.

To create a session for the new patient, users click the link labeled â€œNewâ€ in the patient's record. This opens a record screen, as shown in FIG. 5D. Users record all available clinical information about the patient across the seven domain. In the Symptom Severity domain, users can record up to four Axis I diagnoses and three Axis II diagnoses. Users can also record the patient's symptoms associated with each diagnosis. The invention verifies the diagnosis by indicating whether the symptoms selected meet the DSM-IV CR criteria for the diagnosis. The invention also indicates whether the symptoms are â€œsuggestive ofâ€ the diagnosis by meeting a certain threshold, for example, 70% of the necessary DSM criteria, or simply do not meet the criteria for the diagnosis.

This information is valuable for (a) clinical training, (b) case reviews between providers, and (c) avoiding denials from managed care. To record the patient's diagnoses, users click on the link in Item 2 labeled â€œSelect one or more axis I diagnosesâ€ . This link opens the Axis I fields screen, as shown in FIG. 5E. Clicking on the link again closes the fields to reduce the vertical space of the window. A similar link and fields are available to record Axis II diagnoses.

To enter a primary diagnosis, users click on a link labeled â€œPrimaryâ€ . This opens a window that displays a DSM-IV diagnoses by category in an expandable tree format, as shown in FIG. 5F. Clicking on a category displays the diagnoses or subcategories beneath it, as shown in FIG. 5G.

Clicking on one of the diagnoses closes the selection window and returns focus to the record with the selected diagnosis displayed in the Primary diagnosis field.

To indicate the symptoms associated with the diagnosis and verify the diagnosis, users click a link labeled â€œVerify Symptomsâ€ . This opens a Symptom selection window, as shown in FIG. 5H. Users click the check boxes indicating the symptoms and conditions associated with the diagnosis, and then click Submit. This window closes and focus returns to the record. Users then indicate the severity of the diagnosis using the far right drop down box.

I short, in FIG. 5D, question 2 highlights that an Axis I DSM Diagnosis can be selected; FIG. 5E expands the choices, that up to 4 Axis I diagnoses can be selected; FIG. 5F shows the tree view of the diagnoses in â€œTop Ten Diagnosesâ€ ; FIG. 5G depicts the expanded diagnoses tree; and finally FIG. 5H illustrates the Diagnostic criteria and associated Symptoms for a particular selected Diagnosis.

When all available information is recorded for the domain, users click Next at the bottom or top of the page. The system progresses to the next domain, which is shown in the tabs at the top of the page, and by the â€œSteps Completedâ€ indicator below the tabs and next to the Next button, as shown in FIG. 5I. The next domain is labeled â€œLethalityâ€ and is displayed in the exemplary screen of FIG. 5I.

The Lethality screen of FIG. 5I is used primarily to record information about danger to self, others, or being gravely disabled. The items capture information about the degree and nature of the patient's risk, and history of behavior. When users complete their data entry on this page, they click the Next button.

The next domain, labeled PsychoSocial Support and shown in FIG. 5J, is used to record information about home or living environment; whether the patient lives alone or with others, whether the environment is a source of stress or can provide safety to the patient.

An exemplary Functional Impairment domain screen is depicted in FIG. 5K. Information recorded here pertains to the patient's ability to perform daily living activities and fulfill role responsibilities. It also asks about sources of stress, such as, relationship, work, financial, legal, children, etc.

An exemplary domain labeled Medical Conditions is shown in FIG. 5L. This domain is used to record co-morbid medical conditions and whether they might exacerbate or be exacerbated by the patient's mental health condition. It also asks about the whether the patient is decompensating and the rate of decompensation.

Each of the five domains presented above generate a severity score that is used in determining level of care and severity, and is presented in the report graph presented later.

The last two domains, labeled Patient Resources and Provider Resources, are used to record information about factors that can ameliorate or exacerbate the patient's condition on each of the previous five domains. Patient Resources domain screen of FIG. 5M focuses on motivation for and compliance with treatment, and possible cognitive deficits that might interfere with treatment.

A Provider Resources domain (shown in FIG. 5N) is used to record information about special services the patient requires for admission to a new level of care or continuation at the same level of care, and whether the patient has received these services in the recent past. It is also used to record basic information about the patient's history of treatment, starting with the most recent treatment and its outcome, to an overview of the patient's entire treatment history and which levels of care met with success or failure.

FIGS. 6A-6F show various exemplary reporting screens, according to some embodiments of the present invention. When users complete entering information on the Provider Resources page and click Next, they have completed recording the clinical data for this session. The invention computes scores for each of the domains and generates a suggested â€œLevel of Careâ€ and â€œIntensity of Service.â€ The invention then begins displaying a summary report based on the user's input. In some embodiments, the report is presented in four sub-sections, or one complete section, as described below.

The first section of the report is a narrative of the information from the first three domains, as shown in FIG. 6A. The second section of the report is a narrative of the information from the next four domains, as shown in FIG. 6B. The third section is a presentation of the domain scores in graphical format, as shown in FIG. 6C.

The domain score graph of FIG. 6C enables users to quickly understand the global status of the patient's condition across all seven domains, instead of focusing on one or two areas (typically, lethality and symptoms). The graph brings to users' attention information that they may not normally have considered, such as impaired role functionality or co-morbid medical conditions.

The fourth section of the report is a presentation of the DSM-IV diagnoses on Axes I, II, and III; the symptoms associated with the primary diagnosis as selected by the user; and the invention determination of whether the diagnosis was verified by the symptoms selected by the user, as shown in FIG. 6D.

After reviewing each section of the report, users are asked to indicate whether they agree or disagree with the invention-suggested level of care and intensity of service. If they disagree, users can select a level of care and intensity of service and record their rationale.

After submitting their response, upon request, the invention presents the full report, which includes the four sections described above combined.

In some embodiments, at the bottom of the invention report are three buttons, two are used to print or email the report. If a managed care company has licensed the invention and set up online report submission, a fourth button will appear to submit the report to the managed care company by transferring the record to their database. Otherwise, users can submit a report by clicking on the Email button, which will generate, for example, a PDF version of the report and send it to a managed care recipient, or any designated recipient, via encrypted email. Managed care companies can configure their systems to respond to report submissions by automatically authorizing care when the user accepts the suggested level of care (LOC), which matches the managed care company's own LOC guidelines, and transfer to care managers only those cases where users disagree with the suggested LOC.

Users at a hospital, facility or large provider group who have an electronic medical record (EMR) system can transfer an invention report into a patient's EMR if this feature has been configured by the hospital, facility or group. In this case, data mapping will be set up to enable the invention system to link to matched patient records in the EMR system, and data fields will be mapped to receive some or all of the invention data and an image of the entire report.

The users can print the invention report. After users have completed their review and print out of the report, the application returns focus to the Patient Manager where users can enter another new patient or search for an existing patient to begin a second, third, or subsequent session or complete an existing incomplete session.

For most inpatient cases, users will need to create a follow-up session within 2 days to report a patient's progress to managed care and to request continued authorization. Users in hospital settings may also need to provide follow-up reports every second or third day for several days until the patient is discharged. For most outpatient cases, and cases at intermediate levels of care, a second or third session may also be required. The invention provides a method to create a 2^nd, 3^rdor subsequent invention session in an extremely rapid manner. Returning to the Patient Manager, users search for and locate the existing patient. Clicking on the link labeled â€œNewâ€ in any of the patient's records (there may be several if more than one session has already been completed) will begin the process to create the next record for the patient.

When the record screen opens, all data from the previous session is displayed and all the fields are editable allowing the user to edit any value. (This is in contrast to viewing a previous record, by clicking on a link in the â€œView Assessmentâ€ column in the Patient Manager, where the data is visible but all the fields are locked preventing the data from being modified.)

In addition, in the subsequent session, values selected in the previous session are highlighted using circles around radio buttons and squares around check boxes. Items that are changes are then highlighted by underlining the stem of the question. This technique enables users to rapidly see the items they have changed, and the previous values in those items should they wish to revert to the previous value or simply compare the new value to the old value. Thus, when creating a subsequent session, users need only change those items that reflect changes in the patient's status.

After recording data in each of the domains, the invention generates a new report reflecting the information in the subsequent session, including the new information. The invention also generates a graph of the domain scores, and includes in the graph the scores from the current session and the previous, for example, two sessions. Thus, the second session will display scores from sessions 1 and 2; the third session will display scores from sessions 1, 2, and 3; the fourth session will display scores from sessions 2, 3, and 4, and so on. FIG. 6E shows a sample of a graph from a third session, displaying scores from sessions 1, 2, and 3.

Showing scores from the current session and the previous two sessions enables users and reviewers to quickly identify trends in the data that reflect important and perhaps unnoticed changes in the patient's status. For example, while clinicians and case management reviewer often focus on a patient's status in critical domains such as Symptom Severity or Lethality, the graph enables them to see that significant changes in other domains such as Patient Resources or Medical Conditions are likely to contribute to a re-admission or relapse.

In some embodiments, the software of the present invention is implemented using .Net Frameworkâ„¢ and Visual Studioâ„¢. ASP.NET MVCâ„¢ Framework is a Model-view-controller framework which allows software developers to build a Web application as a composition of three roles: Model, View and Controller. A Model represents the state of a particular aspect of the application. Frequently, a model maps to a database table with the entries in the table representing the state of the table. A Controller handles interactions and updates the model to reflect a change in state of the application. A View extracts necessary information from a model and renders a user interface to display that.

The ASP.NET MVCâ„¢ Framework couples the models, views and controllers using interface-based contracts, thereby allowing each component to be easily tested independently. The view engine in the MVCâ„¢ framework uses regular .aspx pages to design the layout of the user interface pages onto which the data is composed. However, any interactions are routed to the controllers rather than using the post back mechanism. The software of the present invention may be executed on a client computer, a stand-alone computer and/or a server computer aceesible to the users through the Internet.

In a first domain, Symptom Severity, the user indicates in item 1 that the patient has a mental health diagnosis, as depicted in FIG. 7A. In item 2, the user indicates that the patient has a single Axis 1 diagnosis, for example, Major Depression, Recurrent, Moderate. The user opens the symptom check list and selects a number of symptoms. When the check list is closed, the invention's diagnosis verification process indicates that the symptoms are â€œSuggestiveâ€ of the diagnosis. The user selects Moderate as the level of severity for the diagnosis.

As shown in FIG. 7B, based on the Symptom Severity domain scoring rules, a score of â€œS2â€ (third highest of four levels) is generated. The use then clicks on the Next button at the bottom of the screen to proceed to the Lethality page. On the Lethality page, the user indicates on item 1 that the patient has a clear presence of lethality manifested by danger to self.

On items 2, 3, 4, and 5, the user indicates that the patient has suicidal ideations with plans, currently made no suicidal attempt, but has means to carry out his suicidal plans and has lethal means to do so. On items 7, 8, 9, and 10, the user indicates that the patient is depressed, is not intoxicated, is currently markedly impulsive, and has marked hopelessness.

On items 11 and 12, the user indicates that the patient is currently not engaged in behavior to hurt himself but has a past history of hurting himself. When the user clicks Next to send this information to the server, the system first calculates several derived variables. The response to item 10 generates a variable labeled â€œHopelessnessâ€ equal to 1. The responses to item 7 generate a variable labeled â€œSymptomâ€ equal to 1. The responses to items 8 and 9 generate a variable labeled â€œAlcohol_Impulsiveâ€ equal to 1. A variable labeled â€œFactor4â€ is generated by summing the values of Hopelessness, Symptom, and Alcohol_Impulsive.

Next, a Lethality domain scoring process uses items 1 through 5 and Factor4 to generate a score of â€œL4â€ (highest of four levels). On the third domain, labeled â€œPsychoSocial Supportâ€ , the user indicates on the 6^thitem that the patient's home environment does not have the capability to provide safety if the patient exhibits behavior that is harmful to him/herself or others, or abuses alcohol or drugs. When the user completes all seven domains, the decision processes use the domain scores, derived variables, and raw variables to compute a recommended Level of Care. In the current example, the high lethality score of L4 in combination with the response to item 6 on the PsychoSocial Support domain generates a recommended Level of Care of â€œInpatientâ€ . In this particular case, the S2 domain score did not play a role in determining the recommended level of care because the combination of L4 and PsychoSocial item 6 were sufficient to match one of the decision rules. However, if Lethality were not L4, then the combination of S2 and PsychoSocial item 6 (plus other variables) would result in a level of care of Residential Treatment.

FIGS. 8, 9 and 10 illustrate an exemplary process by which the domain scoring process generates derived variables and domain scores, and then the level of care processes use this input to generate a recommended level of care is displayed in the following three flow diagrams. In each diagram, a decision processes compares the user's input to a series of carefully crafted and organized rules until a match is found. Each rule is composed of a different set of criteria reflecting specific clinical criteria.

FIG. 8 shows an exemplary process flow, implemented by a computer, for comparing a user's input to a series of rules to generate the Symptom Severity domain score, according to some embodiments of the present invention. As shown in the example of FIG. 8, the domain score (S4, S3, S2, or S1) is derived from the total configuration of item responses in the domain. While in general a higher score will result from greater pathology across items, there are also interactions between moderator items that may result in a lower score; for example, the contribution of a severe diagnosis will be moderated if it is not verified.

FIG. 9 shows an exemplary process flow, implemented by a computer, for utilizing a user's input to compute derived variables, and then compared to a series of rules to generate the Lethality domain score, according to some embodiments of the present invention. As depicted, after derived variables and domain stratification scores are computed for each domain, the program then invokes another series of rules to determine the Level of Care.

FIG. 10 illustrates an exemplary process flow, implemented by a computer, for utilizing derived variables and domain scores as input to compute and generate a Level of Care, according to some embodiments of the present invention. In this exemplary figure, each level of care is â€œrepresentedâ€ by a series of process and decision making rules. Each combination of domain scores, items scores, and derived variables resulting from the user's input is compared to the rules for each level of care. The rules are designed to assess the total configuration or â€œclinical pictureâ€ of scores and variables; the rules are not mathematical equations that sum the scores. Seemingly similar combinations of domain scores and items generate different level of care results when one or two key variables differ, as shown in FIG. 10. Furthermore, a domain score of S4 contributes to a level of care of Inpatient in rule IP27 when it appears in combination with P4, high risk home environment on the PsychoSocial Support domain, and severe deficiencies in ability to perform social roles on the Functional Impairment domain. However, when P4 is not present, the same S4 will contribute to contribute to a level of care of Residential Treatment in rule RTC1 when it appears in combination with other specific variables that match the clinical criteria for Residential Treatment. Moreover, when L4 is present in combination with Pq6r1 (PsychoSocial question 6 response 1: the patient's home environment cannot provide safety), that combination alone is sufficient to generate an inpatient level of care result without even considering the S4 score.

In some embodiments, the invention includes five major functional modules: a Login module, an Agency module, an User module, a Patient module, and an assessment module. In some embodiments, â€œUse Caseâ€ documents are used for each module

The Login module holds the authentication information for the application, verifies the user credentials and allows the user to access the application, according to some embodiments of the present invention.

The Agency module holds information of the agency record created in the application agency details like agency name, contact information and login id and password, according to some embodiments of the present invention.

In some embodiments, the User module includes two pages: in its start page, a search page has search option for finding the saved record in the grid and user can click the user record in the grid to edit the existing record, and second page is to create new user. This page gets the details of the user like the contact details, educational details, Security level, user roles played by each user and users photograph.

In some embodiments, the Patient module includes two pages; in it start page is a search page which includes search option for finding the saved patient record in grid and user can click the patient record in the grid to edit the existing record and second page is to create new patient. This page gets the details of the patient like the contact details, Insurance details, etc.

In some embodiments, the Assessment module includes seven domains. Each domain carries set of question and answers. This module is attached to the patient search page along with grid. The user can click the new assessment link to start assessment for the particular patient. The seven exemplary domains are namely:

Symptom Severity

Lethality

Psychosocial Support

Functional Impairment

Medical Condition

Patient Resources

Provider Resources

Each domain has a domain score calculated based on the answer selected in each domain. The scores obtained in each domain are consolidated to prepare the level of care that is needed for the patient. Level of care logic and domain score logic are populated in a database to choose the scenario according the answers given, and generate the level of care for the patient. The user can accept the systems level of care or can deny and save his/her own level of care for the patient.

In some embodiments, Assessment Module Screens are dynamically generated from database values populated in a table (MST_QUESTION table), which stores the question of each domain. A (MST_ANSWER) table stores the answers to each question domain wise. A (IMP_ANSWER) table stores impacted answer values, based on the answers chosen, and a (TRN_ASSESMENT) table stores the values for each domain chosen by the user.

In some embodiments, Symptom Severity domain has two sub pages for its second question answer, one is for choosing the diagnosis and the other is its classification page. Classification answers are populated based on the diagnosis selected by the user. The Diagnosis page uses a (MST_AXIS DIAGNOSIS) table for populating the diagnosis tree view structure and based on the diagnosis chosen by the user, classification page is populated from a (MST_AXIS_CLASS_GROUP) table which holds the question of the classification page. A (MST_AXIS_CLASSIFICATION) table stores the classification answers for the page and a (TRN_AXIS_CLASSIFICATION) table uses the two table values and joins the question and answer for each diagnosis. Answers chosen by the user in the classification page are also saved under another (TRN_ASSESSMENT) table. The tables' structures and variable are shown in detail in the Provisional application, the entire contents of which is already expressly incorporated by reference.

Appendix A explains the domain stratification logic and its related domains in more detail. Appendix B explains the domain stratification logic for substance abuse cases, as an example. Appendix C describes exemplary Level of Care Criteria.

It will be recognized by those skilled in the art that various modifications may be made to the illustrated and other embodiments of the invention described above, without departing from the broad inventive scope thereof. It will be understood therefore that the invention is not limited to the particular embodiments or arrangements disclosed, but is rather intended to cover any changes, adaptations or modifications which are within the scope and spirit of the invention as defined by the appended claims.

Appendix ADomain Stratification LogicSymptom Severity DomainS4

1.Patient has two or more diagnoses with:yes/noa) Axis Ia1) only MH ORa2) only SA OR MH+SAandb) Axis I + Axis II diagnosisyes/nosymptoms meets â€œcriteria metâ€ for at least one of the diagnoses and at least â€œsuggestive â€ for other(s)andsymptoms are severe for at least one of the diagnoses with status = Criteria Met or Suggestiveyes/noand IF patient has an SA diagnosis (applies to all remaining criteria) ...2. Patient is currently using (abusing) alcohol, street drugs, or prescriptiondrugsandITEM 4:3. Patient is in an acute state of intoxication or withdrawal meets â€œCriteria metâ€ or â€œSuggestâ€ requiring immediate medical attention in a medical facility or IP facility1 or more symptoms in column 1 OR2 or more symptoms in column 2

1.Patient has one or more diagnoses with:yes/noa) Axis Ia1) only MH ORa2) only SA OR MH+SAb) Axis II diagnosisandsymptoms meets â€œcriteria metâ€ for at least one of the diagnosesyes/noandsymptoms are moderate for at least one of the diagnoses with status = Criteria Metyes/noand IF patient has an SA diagnosis (applies to ail remaining criteria) ...2. Patient is currently using (abusing) alcohol, street drugs, or prescriptiondrugsandITEM 4:3. Patient is in an acute state of intoxication or withdrawal meets â€œCriteria metâ€ or â€œSuggestâ€ no symptoms checked in column 1 AND1 or more symptoms in column 2OR the patient is not in an acute state of intoxication or withdrawal

1.Patient has one or more diagnoses with:yes/noa) Axis Ia1) only MH ORa2) only SA OR MH+SAb) Axis II diagnosisandsymptoms meets â€œsuggestiveâ€ for at least one of the diagnosesyes/noandsymptoms are moderate for at least one of the diagnoses with status = Suggestiveyes/noSuggestModerate OR NotMeetSevereand IF patient has an SA diagnosis (applies to all remaining criteria) ...2. Patient is currently using (abusing) alcohol, street drugs, or prescriptiondrugsandITEM 4:3. Patient is in an acute state of intoxication or withdrawal meets Meet, Suggest, Not Meet or Not Verifiedno symptoms checked in column 1 AND1 or more symptoms in column 2OR the patient is not in an acute state of intoxication or withdrawal

1.Patient has one or no diagnoses with:yes/noa) Axis Ia1) only MH ORa2) only SA OR MH+SAb) Axis II diagnosisandsymptoms meets â€œmeetâ€ , â€œsuggestâ€ or â€œnot meetâ€ for the diagnosis (any status value)yes/noandsymptoms are moderate or mild for the diagnosis with status = Suggestive or Does Not Meetyes/noand IF patient has an SA diagnosis (applies to all remaining criteria) ...2. Patient is not currently using (abusing) alcohol, street drugs, or prescriptiondrugsand3. Patient is not in an acute state of intoxication or withdrawalyes/no

Lethality DomainL4

There is a clear presence of lethality:Danger to selfyes/noorDanger to othersyes/noas determined by:1. Patient has active suicidal/homicidal plansyes/noormade a suicide attemptand2. Patient has available means to carry outyes/noplans/attempts (suicide only)and3. Plans are lethal (suicide only)yes/noOR Homicidal plans are specificand4. Patient has any 2 of 3 or all 3i) Marked hopelessnessyes/noandii)Depression OR Manic excitementyes/noOR Command hallucinations OR paranoiddelusionsandiii)Presence of alcohol/drug useyes/noOR History of alcohol/drug useyes/noOR Presence of marked impulsivityyes/noOR History of impulsivityyes/no

There is a clear presence of, or potential for,lethality:Danger to selfyes/noorDanger to othersyes/noas determined by:1. Patient has active suicidal/homicidal plansyes/noandno suicide attemptsand2. Patient has no available means to carry outyes/noplans/attemptsand3. Plans are non-lethalyes/noOR Homicidal plans are non-specificand4. Patient has any 2 of 3 or all 3i) Marked hopelessnessyes/noorii) Depression or Manic excitementyes/noor Command hallucinations or paranoiddelusionsoriii) Presence of alcohol/drug useyes/noOR History of alcohol/drug useyes/noOR Presence of marked impulsivityyes/noOR History of impulsivityyes/no

There is a potential for lethality:Danger to selfyes/noorDanger to othersyes/noas determined by:1. Patient has only passive suicidal/homicidalyes/noideations.andno suicidal attemptsand2. Patient has no available means to carry outyes/noplans/attemptsThis criterion is inconsistent with â€œpassive ideationâ€ and will not be includedand3. Plans are non-lethalyes/noThis criterion is inconsistent with â€œpassive ideationâ€ and will not be includedOR homicidal non-specific plansand4. Patient has ONLY 1 of 3i) Marked hopelessnessyes/noorii)Depression or Manic excitementyes/noor Command hallucinations orparanoid delusionsoriii)Presence of alcohol/drug useyes/noOR History of alcohol/drug useyes/noOR Presence of markedyes/noimpulsivityOR History of impulsivityyes/no

There is no presence of lethality:Danger to selfyes/noorDanger to othersyes/noas determined by:1. Patient denies any suicidal/homicidal ideations/plansyes/nono hopelessnessand2. IF Patient has Depression or Manic Excitementyes/noor Command hallucinations or paranoid delusions,there is :i) No intoxicated on alcohol, street drugs, prescriptionyes/nodrugsandii) No history of marked impulsivityyes/noandiii)Not currently engaging in behavior to harm self oryes/noothersOR in a supportive environment that has the abilityto carry out a containment plan if such behaviorshould occur.

PsychoSocial Support DomainP4

1. Patient's symptoms are exacerbated by or are a directyes/noresult of interpersonal conflicts in the home.and2. The home is a high risk environment due to:1 or more:i) Availability/use of alcohol/drugsyes/noorii) History of violenceyes/nooriii)History of abuseyes/nooriv)History of neglectyes/noand3. Patient is a victim of physical, emotional, or sexualabuseor4. the patient is a perpetrator of physical, emotional, orsexual abuseand5. If patient is out of control or engages in behavior thatyes/nois a danger to self or others, there is no ability to providea safe environment or carry out a containment plan forimminent danger to self or others; OR patient lives alone

1. Patient's symptoms are exacerbated by or are a directyes/noresult of interpersonal conflicts in the home.and2. The home is a high risk environment due to:1 or more:i) Availability/use of alcohol/drugsyes/noorii) History of violenceyes/nooriii)History of abuseyes/nooriv)History of neglectyes/noand3. Patient is a victim of physical, emotional, or sexualabuseor4. the patient is a perpetrator of physical, emotional, orsexual abuseand5. If patient is out of control or engages in behavior thatyes/nois a danger to self or others, there is clear ability toprovide a safe environment or carry out a containmentplan for imminent danger to self or others

1. Patient's symptoms are exacerbated by or are a directyes/noresult of interpersonal conflicts in the home.and2. The home is not a high risk environment due to:ONLY 0 or 1 of 3i) Availability/use of alcohol/drugsyes/noorii) History of violenceyes/nooriii)History of abuseyes/nooriv)History of neglectyes/noand3. Patient is NOT a victim of physical, emotional, orsexual abuseand4. the patient is NOT a perpetrator of physical, emotional, orsexual abuseand5. If patient is out of control or engages in behavior thatyes/nois a danger to self or others, there is clear ability toprovide a safe environment or carry out a containmentplan for imminent danger to self or others

1. Patient's symptoms are not exacerbated by or are notyes/noa direct result of interpersonal conflicts in the home.and2. The home is not a high risk environment due to:ONLY 0 of 3i) Availability/use of alcohol/drugsyes/noorii) History of violenceyes/nooriii)History of abuseyes/nooriv)History of neglectyes/noand3. Patient is NOT a victim of physical, emotional, orsexual abuseand4. the patient is NOT a perpetrator of physical, emotional, orsexual abuseand3. If patient is out of control or engages in behavior thatyes/nois a danger to self or others, there is clear ability toprovide a safe environment or carry out a containmentplan for imminent danger to self or others

Functional Impairment DomainF4

1. Patient is unable to perform his/her normal role, to anyyes/nodegree, at home, work, school or social setting.and2. i) Patient has a significant roleyes/noas care giveror care takerandis unable to perform these duties to any degreeyes/noand3. Patient is currently missing work or schoolor4. Patient is currently on work disability or worker'scompensationor5. Patient is currently failing in school or is suspendedfrom schoolAND3 or 4 current stressors

1. Patient is unable to perform his/her normal role only toyes/noa minimal degree at home, work, school or social settingand2. i) Patient has a significant roleyes/noas care giveror care takerandis able to perform these duties only to a minimal degreeyes/noORPatient does not have a significant role as a care giver orcare takerand3. Patient is currently missing work or schoolor4. Patient is currently on work disability or worker'scompensationor5. Patient is currently failing in school or is suspendedfrom schoolAND3 or 4 current stressors

1. Patient is only able to perform his/her normal roleyes/noat home or work or school or social setting to a moderatedegreeorPatient is unable to perform his/her normal roleat home or work or school or social setting to a expected(satisfactory) degreeand2. i) Patient has a significant roleyes/noas care giveror care takerandis able to perform these duties, only to a moderate degreeyes/noORPatient does not have a significant role as a care giver orcare takerand3. Patient has a past history of missing work or schoolor4. Patient has a past history of being on work disability or worker'scompensationor5. Patient is currently failing in school

1. Patient is only able to perform his/her normal roleyes/noat home or work or school or social setting to asatisfactory degreeand2. i) Patient has a significant roleyes/noas care giveror care takerandis able to perform these duties, only to a satisfactoryyes/nodegreeORPatient does not have a significant role as a care giver orcare takerand3. Patient has a past history of missing work or schoolorno history of missinng school and no history of missingworkor4. Patient has a past history of being on work disability or worker'scompensationno history of disability AND no history of work compor5. Patient is currently maintaining passing grades inschool

Medical Conditions DomainM4

1. Patient has a major Parity mental health or Substanceyes/norelated DSM-IV diagnosisand2. comorbid (one or more) medical condition(s) thatis/are poorly controlledand3. i) Patient has marked decompensation from his/heryes/nobaseline MH status and continues to deteriorate at amarkedly rapid rate.orii)Patient with history of previous episode of markedyes/norapid decompensation of the MH condition if nottreated emergently

1. Patient has a major Parity mental health or Substanceyes/norelated DSM-IV diagnosisand2. comorbid (one or more) medical condition(s) thatis/are moderately well controlledand3. Patient has marked decompensation from his/heryes/nobaseline MH status and continues to deteriorate at arate that may require a higher level of care if nottreated emergently.

1. Patient has a major Parity mental health or Substanceyes/norelated DSM-IV diagnosisand2. comorbid (one or more) medical condition(s) thatis/are stable but the stability of the medical condition(s)may be adversely affected by significant delay in MHtreatmentand3. Patient has moderate decompensation from his/heryes/nobaseline MH/SA condition and continues to progressivelydeteriorate without more intensive treatment

1. Patient has a major Parity mental health or Substanceyes/norelated DSM-IV diagnosisOR minor non-Parity MH or SA related DSM-IVdiagnosisand2. comorbid (one or more) medical condition(s) thatis/are stable and chronic are not and would not beadversely affected by the MH/SA treatmentOR no follow up answer regarding effect of delay ontreatmentand3. Patient has progressive (mild) decompensation fromyes/nohis/her baseline MH/SA conditionOR symptoms that are improving toward his/her baselineMH/SA conditionOR reached his/her baseline condition

Appendix BDomain Stratification Logic for Substance Abuse Cases

Do-Ques-IPmaintionConditionCODE(Med)IPPHRTCIOPOPSQ2SA diagnosis (Select severity level - drop downSq2severity1 = 1 or Sq2severity1 = 2â—¯â—¯â—¯â—¯â—¯list) (Severe or Moderate) [use Axis 1 Dx 1 asor Sq2severity1 = 4 or Sq2severity1 = 5primiary SA Dx]ORSA diagnosis (Select severity level - drop downSq2severity1 = 3 or Sq2severity1 = 6â—¯â—¯list) (mild)ANDQ4R1 (currently in acute state of intoxication) orSq4r1 = 1 or Sq4r2 = 1â—¯â—¯â—¯â—¯â—¯R2 (currently in acute state of withdrawal) thatANDCB requires immediate medical attention forSq4c1 = 1â—¯â—¯â—¯â—¯â—¯ANDCB (at least 1Sx in column 1) ORSq4Medical_Unit_symptoms > 0â—¯CB (none in column 1 and at least 2Sxs inSq4Medical_Unit_symptoms = 0 andâ—¯column 2) ORSq4IP_Psych_symptoms > 1CB (none in column 1, 1 in column 2, andSq4Medical_Unit_symptoms = 0 andâ—¯â€œOtherâ€ Sxs of intoxication or withdrawal ORSq4IP_Psych_symptoms = 1 and Sq4c12 = 1CB (none in column 1 or 2) and â€œOtherâ€ Sxs ofSq4Medical_Unit_symptoms = 0 andâ—¯â—¯intoxication or withdrawalSq4IP_Psych_symptoms = 0 and Sq4c12 = 1ANDPQ5R1 OR R2Pq5r1 = 1 or Pq5r2 = 1â—¯â—¯ORR3 OR R4Pq5r3 = 1 or Pq5r4 = 1â—¯â—¯â—¯â—¯â—¯ANDQ6R1 OR R3Pq6r1 = 1 or Pq6r3 = 1â—¯â—¯ORR2Pq6r2 = 1â—¯â—¯â—¯LQ1R2 (a potential for lethality manifest by 1 orLq1r2 = 1 and (Lq1c1 = 1â—¯â—¯â—¯â—¯â—¯more CB1, CB2, CB3)or Lq1c2 = 1 or Lq1c3 = 1)ANDQ2R1(suicidal ideations with plan)Lq2r1 = 1â—¯â—¯â—¯â—¯ORR2 (passive suicidal ideations) OR R3 (noLq2r2 = 1 or Lq2r3 = 1â—¯â—¯suicidal ideations)ANDQ8R1(intoxicated on) (1 or more CB1, CB2, CB3)Lq8r1 = 1 and (Lq8c1 = 1â—¯â—¯â—¯â—¯â—¯(Same as S Q4 R1) ANDor Lq8c2 = 1 or Lq8c3 = 1)ANDSQ4R1(currently in acute state of intoxication)Sq4r1 = 1â—¯â—¯â—¯â—¯â—¯ANDCB requires immediate medical attention forSq4c1 = 1â—¯â—¯â—¯â—¯â—¯ANDCB (at least 1Sx in column 1) ORSq4Medical_Unit_symptoms > 0â—¯CB (none in column 1 and at least 2Sxs inSq4Medical_Unit_symptoms = 0 andâ—¯column 2) ORSq4IP_Psych_symptoms > 1CB (none in column 1, 1 in column 2, andSq4Medical_Unit_symptoms = 0 andâ—¯â€œOtherâ€ Sxs of intoxication or withdrawal ORSq4IP_Psych_symptoms = 1 and Sq4c12 = 1CB (none in column 1 or 2) and â€œOtherâ€ Sxs ofSq4Medical_Unit_symptoms = 0 andâ—¯â—¯intoxication or withdrawalSq4IP_Psych_symptoms = 0 and Sq4c12 = 1ANDLQ11R1 (currently engaged in behavior) (1 or moreLq11r1 = 1 and (Lq11c1 = 1 or Lq11c2 = 1)â—¯â—¯â—¯â—¯â—¯CB1, CB2)ANDQ5CB (plans are by) R1Lq5c1 = 1 and Lq5r1 = 1â—¯â—¯â—¯ORR2Lq5c1 = 1 and Lq5r2 = 1â—¯â—¯â—¯â—¯ANDPQ5R1 OR R2 OR R3Pq5r1 = 1 or Pq5r2 = 1 or Pq5r3 = 1â—¯â—¯ORR4Pq5r4 = 1â—¯â—¯â—¯â—¯â—¯ANDQ6R1 OR R3Pq6r1 = 1 or Pq6r3 = 1â—¯â—¯ORR2Pq6r2 = 1â—¯â—¯â—¯MQ2R1 (one or more comorbid conditions that areMq2r6ANDR (poorly controlled) AND S Q4 CB requiresMq2r1 = 1 and Sq4c1 = 1 andâ—¯immediate medical attention for CB (at least 1Sq4Medical_Unit_symptoms > 0Sx in column 1)R (poorly controlled)Mq2r1 = 1â—¯R (moderately well controlled)Mq2r2 = 1â—¯R (stable and chronic)Mq2r3 = 1â—¯â—¯â—¯ANDQ3R1 (marked decompensation/rapid rate) OR R2Mq3r1 = 1 or Mq3r2 = 1â—¯(marked decompensation/emergent Tx)ORR3 (moderate decompensation)Mq3r3 = 1â—¯â—¯â—¯ORR4 (progressive mild decompensatin)Mq3r4 = 1â—¯â—¯ANDSQ2SA diagnosis (Select severity level - drop downSq2severity1 = 1 or Sq2severity1 = 2 orâ—¯â—¯â—¯â—¯list) (Severe or Moderate)Sq2severity1 = 4 or Sq2severity1 = 5ORSA diagnosis (Select severity level - drop downSq2severity1 = 3 or Sq2severity1 = 6â—¯â—¯list) (Mild)ANDQ3Select Frequency (Daily or 3 to 6 Ã— weekly):Sq3frequency1 = 1 or Sq3frequency1 = 2 orâ—¯â—¯â—¯XSELECT HIGHEST Frequence among 4Sq3frequency2 = 1 or Sq3frequency2 = 2 orsubstance fieldsSq3frequency3 = 1 or Sq3frequency3 = 2 orSq3frequency4 = 1 or Sq3frequency4 = 2ORSelect Frequency (1 to 2 Ã— weekly)(Sq3frequency1 = 3 or Sq3frequency2 = 3 orXSq3frequency3 = 3 or Sq3frequency4 = 3) and(Sq3frequency1 <> 1 and Sq3frequency1 <>2 and Sq3frequency2 <> 1 andSq3frequency2 <> 2 and Sq3frequency3 <>1 and Sq3frequency3 <> 2 andSq3frequency4 <> 1 and Sq3freORSelect Frequency (1 to 3 Ã— last 30 days)(Sq3frequency1 = 4 or Sq3frequency2 = 4 orXâ—¯Sq3frequency3 = 4 or Sq3frequency4 = 4) and(Sq3frequency1 <> 1 and Sq3frequency1 <>2 and Sq3frequency1 <> 3 andSq3frequency2 <> 1 and Sq3frequency2 <>2 and Sq3frequency2 <> 3 andSq3frequency3 <> 1 and Sq3freANDQ3Has been continuously using for - less than 1Sq3using_duration = 5â—¯monthORHas been continuously using for - 1-3 month or(Sq3using_duration >= 1 andâ—¯â—¯â—¯â—¯â—¯greater or unknownSq3using_duration <= 4)or Sq3using_duration = 6ANDlongest period of abstinence in past year is lessSq3abstinence_past_year = 1 orâ—¯than 1 month or 1 to 3 monthsSq3abstinence_past_year = 2longest period of abstinence in past year is 3 toSq3abstinence_past_year >= 3 andâ—¯6 months or greater or unknownSq3abstinence_past_year <= 6longest period of abstinence in lifetime is lessSq3abstinence_lifetime = 1â—¯than 1 month or 1 to 3 monthsor Sq3abstinence_lifetime = 2longest period of abstinence in lifetime is 3 to 6Sq3abstinence_lifetime >= 3 andâ—¯â—¯months or greater or unknownSq3abstinence_lifetime <= 6ANDFQ1R1Fq1r1 = 1â—¯ORR2Fq1r2 = 1â—¯â—¯â—¯ORR3 OR R4 OR R5Fq1r3 = 1 or Fq1r4 = 1 or Fq1r5 = 1â—¯â—¯ANDPTQ1R1 OR R2PTq1r1 = 1 or PTq1r2 = 1â—¯â—¯ORR3 OR R4PTq1r3 = 1 or PTq1r4 = 1â—¯â—¯â—¯â—¯ANDQ2R1 OR R2PTq2r1 = 1 or PTq2r2 = 1â—¯â—¯ORR3 OR R4PTq2r3 = 1 or PTq2r4 = 1â—¯â—¯â—¯â—¯ANDQ3R1 and R(interferes) any of 2 of 3 CB [2 orPTq3r1 = 1 and PTq3r5 = 1 and (PTq3c1 +â—¯â—¯more]PTq3c2 + PTq3c3 >= 2)ORR2 and R(interferes) any of 1 of 3 CB [1 orPTq3r2 = 1 and PTq3r5 = 1 and (PTq3c1 +â—¯â—¯â—¯more]PTq3c2 + PTq3c3 >= 1)

Do-Ques-IPmaintionConditionCODE(Med)IPPHRTCIOPOPPTQ4R1 (on an invol hold) and CB1 OR CB2 OR CB3PTq4r1 = 1 and (PTq4c1 = 1 or PTq4c2 = 1 orâ—¯PTq4c3 = 1)ANDSQ4R1 (Sq4r1: acute state of intoxication)Sq4r1 = 1â—¯ORQ4R2 (Sq4r2: acute state of withdrawal)Sq4r2 = 1â—¯ORLQ8R1 (in acute state of intoxication) and CB1 ORLq8r1 = 1 and (Lq8c1 = 1 or Lq8c2 = 1 orâ—¯CB2 OR CB3Lq8c3 = 1)PRQ2Q2 Most recent level of care is â€œDetox/InpatientPRq2LOC = 3â—¯â—¯â—¯Rehabâ€ ANDQ3if history of failure is PH or RTC and months(PRq3c3 = 1 or PRq3c4 = 1) andâ—¯â—¯â—¯since last failure is 0-3 months(PRq3mslf3 = 1 or PRq3mslf4 = 1)ORif history of failure is PH or RTC and months(PRq3c3 = 1 and (PRq3mslf3 = 2 orâ—¯â—¯â—¯since last failure is 3-6 months or morePRq3mslf3 = 3)) or (PRq3c4 = 1and (PRq3mslf4 = 2 or PRq3mslf4 = 3))ORif history of failure is IOP and months since lastPRq3c6 = 1 and PRq3mslf6 = 1â—¯â—¯â—¯failure is 0-3 monthsORif history of failure is IOP and months since lastPRq3c6 = 1 and (PRq3mslf6 = 2 orâ—¯â—¯failure is 3-6 months or morePRq3mslf6 = 3)ANDQ1R1 and CB1 with subsequent CB1 or CB2 orPRq1r01 = 1 and PRq1c1 = 1 andâ—¯CB3(PRq1c2 = 1 or PRq1c3 = 1 orPRq1c4 = 1)ORR1 and CB2 with subsequent CB1 or CB2PRq1r01 = 1 and PRq1c5 = 1 andâ—¯(PRq1c6 = 1 or PRq1c6 = 1)ORR1 and CB4 with subsequent CB1 or CB2PRq1r01 = 1 and PRq1c9 = 1 andâ—¯â—¯(PRq1c10 = 1 or PRq1c11 = 1)ORR1 and CB3PRq1r01 = 1 and PRq1c8 = 1â—¯â—¯â—¯ORR1 and CB5 OR CB6PRq1r01 = 1 and (PRq1c12 = 1â—¯â—¯or PRq1c13 = 1)

Do-Ques-IPmaintionConditionCODE(Med)IPPHRTCIOPOPPRQ2Q2 Most recent level of care is â€œDetox/InpatientPRq2LOC = 3â—¯â—¯â—¯Rehabâ€ ANDQ3if history of failure is PH or RTC and months(PRq3c3 = 1 or PRq3c4 = 1) andâ—¯â—¯â—¯since last failure is 0-3 months(PRq3mslf3 = 1 orPRq3mslf4 = 1)ORif history of failure is PH or RTC and months(PRq3c3 = 1 and (PRq3mslf3 = 2 orâ—¯â—¯â—¯since last failure is 3-6 months or morePRq3mslf3 = 3)) or (PRq3c4 = 1 and(PRq3mslf4 = 2 or PRq3mslf4 = 3))ORif history of failure is IOP and months since lastPRq3c6 = 1 and PRq3mslf6 = 1â—¯â—¯â—¯failure is 0-3 monthsORif history of failure is IOP and months since lastPRq3c6 = 1 and (PRq3mslf6 = 2 orâ—¯â—¯failure is 3-6 months or morePRq3mslf6 = 3)ANDQ1R1 and CB1 with subsequent CB1 or CB2 orPRq1r01 = 1 and PRq1c1 = 1 andâ—¯CB3(PRq1c2 = 1 orPRq1c3 = 1 or PRq1c4 = 1)ORPRQ2Q2 Most recent level of care is â€œDetox/InpatientPRq2LOC = 3â—¯â—¯Rehabâ€ ANDQ3if history of failure is PH or RTC and months(PRq3c3 = 1 or PRq3c4 = 1) andâ—¯since last failure is 0-3(PRq3mslf3 = 1 or PRq3mslf4 = 1)ORif history of failure is PH or RTC and months(PRq3c3 = 1 and (PRq3mslf3 = 2 orâ—¯â—¯since last failure is 3-6 months or morePRq3mslf3 = 3)) or (PRq3c4 = 1 and(PRq3mslf4 = 2 or PRq3mslf4 = 3))ORif history of failure is IOP and months since lastPRq3c6 = 1 and PRq3mslf6 = 1â—¯â—¯failure is 0-3 or 3-6ORif history of failure is IOP and months since lastPRq3c6 = 1 and (PRq3mslf6 = 2 orâ—¯â—¯failure is 3-6 months or morePRq3mslf6 = 3)ANDQ3number of episodes in SA Detox/Rehab 3 orPRq3noe9 >= 3â—¯XmoreORnumber of episodes in SA Detox/Rehab 0 to 2PRq3noe9 <= 2Xâ—¯ANDPQ2R1 (high risk environment) AND FIRST CHECKPq2r1 = 1 and Pq2c1 = 1 and (Pq2c2 = 1â—¯â—¯BOX, and then CB1 OR CB2 OR CB3 focus onor Pq2c3 = 1 or Pq2c12 = 1)alc/drug abuseORR2 (not a high risk environment)Pq2r2 = 1â—¯â—¯ANDQ6R1 OR R3Pq6r1 = 1 or Pq6r3 = 1â—¯ORR2Pq6r2 = 1â—¯â—¯

Appendix CLevel of Care Criteria

IP: InpatientPsychoSocialFunctionalMedicalPatientProviderSymptomsLethalitySupportImpairmentConditionsResourcesResourcesIPDomain 1Domain 2Domain 3Domain 4Domain 5Domain 6Domain 7Do-S4 or S3 orLq2r1PRq1r01 and PRq1c1 and PRq1c2main 1S2 or S1S4 or S3 orLq11r1 andPRq1r01 and PRq1c1 and PRq1c2S2 or S1(Lq11c1 or Lq11c2)S4 or S3 orPRq1r01 and PRq1c1 and (PRq1c3 or PRq1c4)S2 or S1S4 or S3 orPRq1r01 and PRq1c5 and PRq1c6S2 or S1S4 or S3 orLq2r1PRq1r02 and PRq1c1 and PRq1c2 and PRq1r1S2 or S1S4 or S3 orLq11r1 andPRq1r02 and PRq1c1 and PRq1c2 and PRq1r1S2 or S1(Lq11c1 or Lq11c2)S4 or S3 orPRq1r02 and PRq1c1 and ((PRq1c3 andS2 or S1PRq1r4) or (PRq1c [Image Omitted]

S4 or S3 orPRq1r02 and PRq1c5 and PRq1c6 andS2 or S1PRq1r10S4 or S3 orPRq1r02 and PRq1c8 and PRq1r16S2 or S1S4(PRq2LOC >= 1 and PRq2LOC <= 5) and(PRq2OUTCOME [Image Omitted]

S3 or S2(PRq2LOC >= 1 or PRq2LOC <= 3) and(PRq2OUTCOME > [Image Omitted]

Do-LF REMOVED THE CONDITIONmain 2THAT REQUIRED ONLY L4L4 or L3PRq1r01 and PRq1c1 and PRq1c2L4 or L3PRq1r01 and PRq1c5 and PRq1c6L4 or L3PRq1r01 and PRq1c8L4 or L3 and (Lq11r1 andPRq1r02 and PRq1c1 and PRq1c2 and(Lq11c1 or Lq11c2))PRq1r1L4 or L3PRq1r02 and PRq1c5 and PRq1c6 andPRq1r10L4 or L3PRq1r02 and PRq1c8 and PRq1r16L4 or L3(Pq6r1 or Pq6r3or Pq5r1)Do-Lq11r1 andP4main 3(Lq11c1 or Lq11c2)S4P4Fq1r1 and (Fq1c1 orFq1c2 or Fq1c3)S4P4Fq2r1 and (Fq2c1 or Fq2c2)and (Fq2r2 or (Fq2r3 and Fq2r4))S4P4Fq3r1 and (Fq3c1 orFq3c2)S4P4Fq7r1 or Fq7r2S4P4Fq8r1Do-F4 or F3(PTq3r1 or PTq3r2) and PTq3r5.(PRq3c3 = 1 andmain 4PRq3c11 = 1 and PRq3mslf3 = 1) or (PRq3 [Image Omitted]

F4 or F3(PTq3r1 or PTq3r2) and PTq3r5.((PRq3c3 = 1 andPRq3c11 = 1 and PRq3mslf3 > 1) or (PRq [Image Omitted]

Do-S4 or S3Pq5r1 or Pq5r2M4 or M3(PTq3r1 or PTq3r2) and PTq3r5.(PRq3c3 = 1 andmain 5PRq3c11 = 1 and PRq3mslf3 = 1) or (PRq3 [Image Omitted]

S4 or S3Pq5r1 or Pq5r2M4 or M3(PTq3r1 or PTq3r2) and PTq3r5.(PRq3c3 = 1 andPRq3c11 = 1 and PRq3mslf3 > 1) or (PRq3 [Image Omitted]

Do-PTq4r1 and (PTq4c1 or PTq4c2 or PTq4c3)main 6Lq11r1 andPq6r1 or Pq6r3(PTq4r2 or PTq4r3) and (PTq4c1 or PTq4c2(Lq11c1 or Lq11c2)or PTq4c3)Do-main 7 [Image Omitted]

indicates data missing or illegible when filed

RTC: Residential Treatment CenterPsychoSocialFunctionalMedicalPatientProviderSymptomsLethalitySupportImpairmentConditionsResourcesResourcesRTCDomain 1Domain 2Domain 3Domain 4Domain 5Domain 6Domain 7Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2)PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r01 =main 1an [Image Omitted]

â€‰Pq6r1 = 1 or Pq6r3 = 1 or Pq5r1 = 11 and ((PRq1c5 = 1 and PRq1c7 = 1) or PRq1c8 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2)PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r01 =an [Image Omitted]

â€‰Pq6r1 = 1 or Pq6r3 = 1 or Pq5r1 = 11 and ((PRq1c5 = 1 and PRq1c7 = 1) or PRq1c8 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2)PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r02 =an [Image Omitted]

â€‰Pq6r1 = 1 or Pq6r3 = 1 or Pq5r1 = 11 and (((PRq1c5 = 1 and (PRq1c7 = 1 and (PRq1 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2)PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r02 =an [Image Omitted]

â€‰Pq6r1 = 1 or Pq6r3 = 1 or Pq5r1 = 11 and (((PRq1c5 = 1 and (PRq1c7 = 1 and (PRq1 [Image Omitted]

Do-Lethality = 3 orPsychSocial = 4PRq1r01 = 1 and ((PRq1c5 =main 2Lethality = 21 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

Lethality = 3 orPsychSocial = 4PRq1r01 = 1 and ((PRq1c5 =Lethality = 21 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

Lethality = 3 orPsychSocial = 4PRq1r02 = 1 and (((PRq1c5 =Lethality = 21 and (PRq1c7 = 1 and (PRq1 [Image Omitted]

Do-main 3Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3(PTq3r4 = 1 or ((PTq3r1 = 1 or P [Image Omitted]

â€‰(PRq3c3 =main 4S [Image Omitted]

â€‰Pq5r1 = 1 or Pq5r2 = 11 and PRq3c11 = 1 and PRq3mslf3 = 1) or (PRq3 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3(PTq3r4 = 1 or ((PTq3r1 = 1 or P [Image Omitted]

â€‰((PRq3c3 =S [Image Omitted]

â€‰Pq5r1 = 1 or Pq5r2 = 11 and PRq3c11 = 1 and PRq3mslf3 > 1) or (PRq [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3(PRq3c3 = 1 and PRq3c11 = 1S [Image Omitted]

â€‰PsychSocial = 4and PRq3mslf3 = 1) or (PRq3 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3((PRq3c3 = 1 and PRq3c11 = 1S [Image Omitted]

â€‰PsychSocial = 4and PRq3mslf3 > 1) or (PRq [Image Omitted]

Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andMedical = 3 orPRq1r01 = 1 and ((PRq1c5 =main 5S [Image Omitted]

â€‰Pq2r1 = 1 and (Pq2c1 = 1 or Pq2c4 = 1 or Pq2c7Medical = 21 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andMedical = 3 orPRq1r01 = 1 and ((PRq1c5 =S [Image Omitted]

â€‰Pq2r1 = 1 and (Pq2c1 = 1 or Pq2c4 = 1 or Pq2c7Medical = 21 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andMedical = 3 orPRq1r02 = 1 and (((PRq1c5 =S [Image Omitted]

â€‰Pq2r1 = 1 and (Pq2c1 = 1 or Pq2c4 = 1 or Pq2c7Medical = 21 and (PRq1c7 = 1 and (PRq1 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andMedical = 3 orPRq1r02 = 1 and (((PRq1c5 =S [Image Omitted]

â€‰Pq2r1 = 1 and (Pq2c1 = 1 or Pq2c4 = 1 or Pq2c7Medical = 21 and (PRq1c7 = 1 and (PRq1 [Image Omitted]

Do-main 6Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) and Sq4r1 <> 1 and (Sq4MedicFq1r2 = 1 andmain 7(Fq1c1 = 1 or Fq1c2 = 1 or Fq1 [Image Omitted]

â€‰PTq3r4 = 1 or ((PTq3r1 = 1 or PT (PRq1r01 = 1 and((PRq1c5 = 1 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) and Sq4r1 <> 1 and (Sq4Medic Fq1r2 = 1 and(Fq1c1 = 1 or Fq1c2 = 1 or Fq1 [Image Omitted]

â€‰PTq3r4 = 1 or ((PTq3r1 = 1 or PT (PRq1r01 = 1 and((PRq1c5 = 1 and PRq1c7 = 1) or PRqc8 [Image Omitted]

indicates data missing or illegible when filed

PH: Partial Hospital ProgramPsychoSocialFunctionalMedicalPatientProviderSymptomsLethalitySupportImpairmentConditionsResourcesResourcesPHDomain 1Domain 2Domain 3Domain 4Domain 5Domain 6Domain 7Do-(Symptoms = 4 or Symptoms = 3 or(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

PRq1r01 = 1main 1Symptoms = 2) an [Image Omitted]

â€‰Pq6r2 = 1and ((PRq1r5 = 1 and PRq1r7 = 1) or PRq1r8 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

â€‰PRq1r01 = 1Symptoms = 2) an [Image Omitted]

â€‰Pq6r2 = 1and ((PRq1r5 = 1 and PRq1r7 = 1) or PRq1r8 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

â€‰PRq1r02 = 1Symptoms = 2) an [Image Omitted]

â€‰Pq6r2 = 1and ((PRq1c5 and PRq1c7 and PRq1r13) or (P [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

â€‰PRq1r02 = 1Symptoms = 2) an [Image Omitted]

â€‰Pq6r2 = 1and ((PRq1c5 and PRq1c7 and PRq1r13) or (P [Image Omitted]

Do-L3 or L2P3PRq1r01 = 1 and ((PRq1r5 = 1 andmain 2PRq1r7 = 1) or PRq1r8 = [Image Omitted]

L3 or L2P3PRq1r01 = 1 and ((PRq1r5 = 1 andPRq1r7 = 1) or PRq1r8 = [Image Omitted]

L3 or L2P3PRq1r02 = 1 and ((PRq1c5 and PRq1c7and PRq1r13) or (P [Image Omitted]

Do-main 3Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

â€‰((PRq3c5 = 1main 4S [Image Omitted]

â€‰Pq5r4 = 1and PRq3c13 = 1 and PRq3mslf5 = 1) or (PRq [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andF4 or F3(PTq1r3 = 1 or PTq1r4 = 1) and ( [Image Omitted]

â€‰((PRq3c5 = 1S [Image Omitted]

â€‰Pq5r4 = 1and PRq3c13 = 1 and PRq3mslf5 > 1) or (PRq [Image Omitted]

Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andM4PRq1r01 = 1 and ((PRq1r5 = 1 andmain 5Sq4r1 <> 1 and (Sq4Medical_Unit_symptoms = 0 a [Image Omitted]

PRq1r7 = 1) or PRq1r5 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andM4PRq1r01 = 1 and ((PRq1r5 = 1 andSq4r1 <> 1 and (Sq4Medical_Unit_symptoms = 0 a [Image Omitted]

PRq1r7 = 1) or PRq1r5 = [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) andM4PRq1r02 = 1 and ((PRq1c5 and PRq1c7Sq4r1 <> 1 and (Sq4Medical_Unit_Symptoms = 0 a [Image Omitted]

and PRq1r13) or (P [Image Omitted]

(Symptoms = 4 or Symptoms = 3M4PRq1r02 = 1 and ((PRq1c5 and PRq1c7or Symptoms = 2) andand PRq1r13) or (P [Image Omitted]

Sq4r1 <> 1 and (Sq4Medical_Unit_Symptoms = 0 a [Image Omitted]

Do-main 6Do-(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) and Sq4r1 <> 1 and (Sq4Medic Fq1r2 andmain 7(Fq1c1 or Fq1c2 or Fq1c3 or Fq1c4 PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r01 = 1 and((PRq1c5 = 1 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

(Symptoms = 4 or Symptoms = 3 or Symptoms = 2) and Sq4r1 <> 1 and (Sq4MedicFq1r2 and(Fq1c1 or Fq1c2 or Fq1c3 or Fq1c4 PTq3r4 = 1 or ((PTq3r1 = 1 or PT PRq1r01 = 1 and((PRq1c5 = 1 and PRq1c7 = 1) or PRq1c8 [Image Omitted]

indicates data missing or illegible when filed

IOP: Intensive OutpatientPsychoSocialFunctionalSymptomsLethalitySupportImpairmentIOPDomain 1Domain 2Domain 3Domain 41Domain 1S4 or S32S2 or S13Domain 2L3 or L2 or L1(#3) in P3 or P24Domain 3P35(#1 or #2)in S4 or S3P26P2(#1 or #2)in F4 or F37P28Domain 4(#3) in P3 or P2F49F3 or F2 or F110Domain 5L4 or L3 or L2 not present11L4 OR L3 OR L2(#3) in P3 or P21213Domain 6L214P215S1L116L1F117L118S1L2 or L3(#3) in P3 or P219L2 or L3(#3) in P3 or P2F120L2 or L3(#3) in P3 or P2Domain 7MedicalPatientProviderConditionsResourcesResourcesIOPDomain 5Domain 6Domain 71Domain 1Pt(#1 + #2)2Pt(#1 + #2)Pr(#2 OR #3))3Domain 2Pr(#2)4Domain 3Pt(#1 + #2)Pr(#2)5Pt(#1 + #2)6Pt(#1 + #2)7(#1 or #2)in H4 or H3Pt(#1 + #2)8Domain 4Pr(#2)9Pt(#1 + #2)Pr(#2 OR #3))10Domain 5M4 or M3Pr(#2)11M4 or M3Pr(#2)12M2 or M1Pt(#1 + #2)Pr(#2 OR #3))13Domain 6Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))14Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))15Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))16Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))17M1Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))18Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))19Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))20M1Pt(#1 + #2 + #3 + #4)Pr(#2 OR #3))Domain 7

OP: Outpatient ServicesPsychoSocialFunctionalMedicalPatientProviderSymptomsLethalitySupportImpairmentConditionsResourcesResourcesOPDomain 1Domain 2Domain 3Domain 4Domain 5Domain 6Domain 7Domain 1S4S3 or S2 or S1Pt(#1 + #2)Domain 2L3 or L2 or L1(#3) in P3 or P2Domain 3P3Pt(#1 + #2):no/lowmotivation AND no/low complianceS1P2Pt(#1 + #2)P2F1Pt(#1 + #2)P2M1Pt(#1 + #2)Domain 4(#3) in P3 or P2F4F3 or F2 or F1Pt(#1 + #2)Domain 5L4 or L3 or L2 not presentM4 or M3L4 or L3 or L2(#3) in P3 or P2M4 or M3M2 or M1Pt(#1 + #2)Domain 6S1Pt(#1 + #2 + #3 + #4)Pr(#3)L1Pt(#1 + #2 + #3 + #4)Pr(#3)P1 OR P2Pt(#1 + #2 + #3 + #4)Pr(#3)F1Pt(#1 + #2 + #3 + #4)Pr(#3)M1Pt(#1 + #2 + #3 + #4)Pr(#3)L2 or L3(#3) in P3 or P2Pt(#1 + #2 + #3 + #4)Pr(#3)Domain 7