| This tab, 1.Cover Letter, descripes the information in tab 2 of this document. |
|
|
|
| Tab |
|
Description |
| 2.CIMS-NIMH Atr |
Report on the attributes available for selection. Explaination of the report column heads appears below, titled Column Definitions. |
|
|
|
|
Column Definitions |
|
|
|
| Column |
Name |
Description |
| A |
Source |
Name of Data Source |
| B |
SourceTabOrd |
Ordinal Position of Table in Data Dictionary received from Source System-used internally |
| C |
SourceTable |
Name of the Table from which the data element is extracted from Source System |
| D |
SourceFieldOrd |
Ordinal Position of the data element in a Table in the Source System Data Dictionary-used internally |
| E |
FieldName |
Name of the data element (please use the literal format as in the column) |
| F |
PII/HIPAA Sensitive |
Please note YES, NO or DI (De-Identification)for the element PII or HIPAA sensitivity. If the element is PII or HIPAA sensitive and it will be de-identified, enter DI. A blank enter will be considered the same as a NO. |
| G |
NIMH (or USAPHC(Prov)) Approval |
User has accepted this as a valid element for their use-drop down list-Yes or No |
| H |
NIMH (or USAPHC(Prov)) SP2Delta |
Date the data element requested in Spiral-2. This will help in revising your existing extract routines |
| I |
Chosen BY USAPHC (Prov) |
An "X" indicates that the element was chosen byUSAPHC (Prov) for inclusion in their element selection. |
| J |
FieldType |
This is the data type. |
| K |
Nullability |
This is the Nullability condition |
| L |
Primary Key |
Indicator if data element is a primary key (PK) or foreign key (FK) in this table |
| M |
Title |
Data Element Name |
| N |
Desc |
Dictionary meaning of the data element and enumerated values if applicable |
| O |
Values |
Information on values the element may have |
| P |
Notes |
Notes concerning the element |
| Q |
FDM Comments |
Please add any comments that will help us understand the output extract. |
| R |
ADS Comment |
Please add any comments on authoritativeness |
| S |
Code Table Reference |
Reference to code table. |
|
| Note: Please see the xlsx file titled "CIMS Lookup Tables-ASPTF Updated 5 Sep 09-for SM Data Dictionary" for detailed information on CIMS code tables |
| FieldName |
Chosen By USAPHC (Prov) |
Title |
Desc |
Notes |
| vsCaseNumber |
Case |
CaseNumber |
The case number associated with the entity, according to ACI2. An entity may be associated with no cases or multiple cases. The case number consists of three elements: sequence number, year, and CID Unit number. The sequence number is 0001 to 9999, for each unit for each calendar year. These numbers are assigned automatically and sequentially by ACI2 upon case creation. The year is the calendar year when the case was created. The CID Unit number is a three digit number assigned by the US Army Crime Records Center. There are about 160-200 active unit numbers that create reports each year. These unit numbering assignments can change over time, but are generally stable. There was a numbering system for units created years ago, but it is no longer enforced. It is not useful to try to interpret the unit numbers unless one has extensive experience with and historical knowledge of the CID unit numbering system. |
Level - Case |
| lROINumber |
ROI |
ROINumber |
The Report of Investigation number. This is a five digit number. The ROI number is assigned to Significant Data File type cases at the time the Initial ROI report is approved by the Special Agent in Charge (SAC). This number is unique by year for all of CID. Number blocks are assigned by the Crime Records Center each calendar year to each unit. Number blocks are never sequential for units across calendar years. The ROI number is assigned by ACI2 automatically at the time of the Initial ROI report approval. The ROI number is significant for physical case file management as it is used to organize where files are placed on shelves prior to electronic scanning. |
Level - Case |
| lYear |
Year |
CaseYear |
The calendar year in which the case was created. |
Level - Case |
| sCode |
CIDInvUnit |
Unit |
The investigating CID Unit number that created the case in which the entity appears. |
Level - Case |
| tblVOWSOffenseFinding.various |
AdjElig |
4833Eligible or AdjElig |
An indicator of whether the entity is adjudication eligible. If so, then marked yes. An entity is eligible when they have at least one founded offense within the case. |
Level - Entity |
| vsNameFirst-FoundFirstName |
FoundFirstName |
FoundFirstName |
The first name of the person found in ACI2 that is associated with the search criteria provided. More than one name might match the search criteria, such as John R Smith and Jack R Smith. |
Level - Entity |
| vsNameLast |
FoundLastName |
FoundLastName |
The middle name of the person found in ACI2 that is associated with the search criteria provided. More than one name might match the search criteria, such as John R Smith and John F Smyth. |
Level - Entity |
| vsNameMiddle-FoundMiddleName |
FoundMiddleName |
FoundMiddlename |
The middle name of the person found in ACI2 that is associated with the search criteria provided. More than one name might match the search criteria, such as John R Smith and John F Smith. |
Level - Entity |
| tblAddress.various-IncAddress |
IncidentLocation |
IncAddress |
The full address of the type indicated. This is an artificially constructed field. The address type is described in the column header, such as IncAddress stands for Incident Address. There are many address types in ACI2 but all have the same format, so they are repeated in many columns that differ only by address type. |
Level - Incident |
| dtEnd-IncEndDate |
IncEndDate |
IncEndDate |
The date an incident ended. Not mandatory - may be blank. See details under IncStartDate. |
Level - Incident |
| dtStart-IncStartDate |
IncStart |
IncStartDate |
The date an incident began. An incident is a time and location container for offenses. The start time is based on the information the investigator collects and is a judgment of the earliest time relevant to the investigation. This time may not coincide with when an offense occurred. ACI2 does not record the date/time when offenses occur. In some circumstances, when the incident start and end date/time values are close (the period of the incident is small), the date and time of an offense can be narrowed down. For example, if an incident starts and end on the same day between 0700 and 0730 hours, by deduction, the offense(s) within the incident occurred during those 30 minutes. This is actually a parsed element of the date/time field in ACI2. This is a mandatory field in ACI2. |
Level - Incident |
| sCode |
InvFinding |
OffFinding |
The code of the investigative finding for the count shown. Each offense count must receive an investigative finding by the investigator before the case is finalized. Four findings are possible: F = FOUNDED. U = UNFOUNDED. IF (sic for IE) = Insufficient Evidence. UI = Under Investigation. The exact definitions and criteria for these findings are in CID Regulation 195-1, Chapter 8. Findings can be given at the offense or count level. For count findings, see paragraph 8-6 e (1-3). FOUNDED: The investigation determined probable cause that an individual committed the offense under investigation. UNFOUNDED: The investigation determined probable cause that an individual did not commit the offense under investigation. INSUFFICIENT EVIDENCE: The inability to establish probable cause to believe that a certain person listed in the subject/suspect block for committing an offense, did or did not commit the offense. FOR REFERENCE ONLY - not applicable to this column, but for general reference - offense findings use the same words but are defined with different language, see Paragraph 8-6 d. (1-4). Roughly, the language is: FOUNDED: A determination made by CID that a criminal offense has been committed. The determination that a founded offense exists is an investigative decision independent of any judicial opinion or disciplinary action. UNFOUNDED: A determination made by CID that a criminal offense did not occur. A lack of evidence to support a complaint or questioning of certain elements of a complaint is not sufficient to categorize an incidents as unfounded. INSUFFICIENT EVIDENCE: The inability of the investigation to determine that reported or alleged criminal offense did or did not occur. Additional criteria must be met; see CID Regulation 195-1, paragraph 7-11 b (1). UNDER INVESTIGATION: CID has not provided an opinion on the offense as recorded in ACI2. |
Level - Instance |
| vsSSN-FoundSSN |
FoundSSN |
FoundSSN |
The SSN in ACI2 that was found to match the requested SSN. Logically, this field will always match the Requested SSN if the SSN match search was successful. Otherwise, this field is left blank. If this field is blank, then all other reporting fields are logically blank as well. CAUTION: Because of data entry errors or missing data validation in various systems, completely different people may be reported for the same SSN or the same person may be reported under two different SSNs in a database. Data requesters must consider these logical possibilities when interpreting data. There are at least four logical errors that requesters make from common false assumptions. Data requesters are reminded to avoid invalid conclusions that follow from fallacious logic tied to these four false assumptions: 1) SSNs are unique; 2) Failure to match an SSN means the person is not in the target database; 3) Every instance of the same person in a database will always have the same SSN; 4) Every instance of a person in a database will always have the same name. The Crime Records Center is ready to help if there are questions about how to interpret data. |
Level - MetaData |
| vsArmyOffenseCode-OffCode |
OffCode |
OffCode |
The Offense Code. Generally, these offense codes are similar to those found in the offense table list in AR 190-45, law enforcement reporting. Codes are used by the Office of the Provost Marshal General (OPMG) for quick reference to and categorization of types of criminal activity. They are also useful for organizing law enforcement reports. |
Level - Offense |
| vsReport-OffName |
OffenseDescription |
OffName |
An English description of the alleged offense. Generally, these offense descriptions are similar to those found in the offense table list in AR 190-45, law enforcement reporting. |
Level - Offense |
| vsMake |
Make |
PropertyMake |
The property make (manufacturer name) entered into ACI2. This is a free text entry. |
Level - Property |
| vsModel |
Model |
PropertyModel |
The property model (manufacturer's model name/number) entered into ACI2. This is a free text entry. |
Level - Property |
| dQuantity |
Qty |
PropertyQty |
The property quantity entered into ACI2. This is a number value. |
Level - Property |
| vsDescription |
MeasureType |
PropertyQtyMeasureType |
The property quantity measure type selected in ACI2. This is normally EA for each. |
Level - Property |
| vsDescription |
PropertyType |
DrugType |
The drug type shown in the property section of the case in which the entity appears that matches search criteria. This may or may not be the drug associated with the entity shown. You CANNOT assume this is a drug associated with the entity; you have to check the facts of the case. Drugs are not associated with individuals; they are associated with incidents within cases. Only the narrative can provide a positive association between a drug and a person. |
Level - Property |
| tblVOWSOffenseFinding.various and tblReferral.various |
SancElig |
Sanction Eligible |
An indicator of whether the entity is sanction eligible. If so, then marked Yes. An entity is eligible when they are adjudication eligible (have at least one founded offense within the case) and have at least one offense accepted and have at least one offense with a trial finding of guilty. Otherwise, sanctions are not logically possible. However, a commander may impose sanctions without accepting offenses - while this violates policy, we see it occur administratively from time to time. The purpose of this data element is to help the requester to understand if it is logically possible for an allged offender to receive a sanction. Often, non-LE personnel assume an allegation should result in punishment. That is a false assumption. |
Level - Referral |
| dtDecisionDate |
CdrDecisiondate |
CdrDecisionDate |
The date the Commander enters on the form, or if missing, the date the commander signs the form. The information comes from the commander. A CID user transcribes the commander’s information into ACI2 after the form is returned from the commander. |
Level - Referral |
| dtReferralDate |
ReferredDate |
ReferralDate |
The date the system user generates the referral form in ACI2. By default, the current date. ACI2 populates this information automatically for the user based on the date on the local computer. |
Level - Referral |
| dtSuspenseDate |
SuspenseDate |
SuspenseDate |
The date the referral form is due back from the commander, in accordance with AR 190-45, Law Enforcement Reporting. By default, the suspense is 45 days after the referral date. ACI2 populates this information automatically for the user based on the date on the local computer. A user can change the suspense date later in the process if necessary, such as when a trial date cannot be set for months. |
Level - Referral |
| RECEIVED |
ReferredSSN |
RequestedSSN |
The SSN provided by the data requester used as a search criterion for finding matching entities in ACI2. |
Level - Requester |
| vsNameFirst-RequestedFirstName |
ReferredFirstName |
RequestedFirstName |
The First Name provided by the data requester. This is not used for searching. Only the SSN is used for exact match searching. This information is echoed back to the data requester to assist in visual or electronic comparisons of found names. |
Level - Requester |
| vsNameLast-RequestedLastName |
ReferredLastName |
RequestedLastName |
The Last Name provided by the data requester. This is not used for searching. Only the SSN is used for exact match searching. This information is echoed back to the data requester to assist in visual or electronic comparisons of found names. |
Level - Requester |
| vsNameMiddle-RequestedMiddleName |
ReferredMiddleName |
RequestedMiddleName |
The Middle Name provided by the data requester. This is not used for searching. Only the SSN is used for exact match searching. This information is echoed back to the data requester to assist in visual or electronic comparisons of found names. |
Level - Requester |
| tblSanctionsReferral.bSuspended |
Suspended |
SanctionsSuspended |
Marked Yes if so indicated by the commander on the returned DA Form 4833. |
Level - Sanction |
| vsGrade-GradeReductionTo |
NewGrade |
GradeReductionTo |
The grade of the offender after the imposition of the punishment. |
Level - Sanction |
| vsGrade-GradeReductionFrom |
OldGrade |
GradeReductionFrom |
The grade of the offender before the imposition of the punishment. This data is stored in tblPayPlanRef.vsGrade (or a full description under vsDescription). |
Level - Sanction |
| vsDescription |
DischargeCharacterization |
DischargeCharacterization |
The characterization of the discharge as entered by the commander. |
Level - Sanction |
| vsDescription-SeparationChapter |
DischargeChap |
SeparationChapter |
The chapter within the regulation that is the basis for administrative separation of the offender. |
Level - Sanction |
| vsDescription-SeparationRegulation |
DischargeReg |
SeparationRegulation |
The regulatory authority for administrative separation of the offender; there are two basic regulations, one for officers and another for enlisted . |
Level - Sanction |
| vsDescription-SanctionDurationType |
SanctionDuration |
SanctionDurationType |
The unit of duration measurement as days, months, or years. |
Level - Sanction |
| vsDescription-SuspenseDurationType |
SuspendedDuration |
SuspenseDurationType |
The unit of duration measurement as days, months, or years. |
Level - Sanction |
| vsDescription-TypeReprimandAction |
SanctionType |
TypeReprimandAction |
This is inferred by the selection of Oral, Local, or OMPF. |
Level - Sanction |
| dtDischargeEffectiveDate |
DischargeEffectiveDate |
DischargeEffectiveDate |
The effective date of the discharge as entered by the commander. |
Level - Sanction |
| mMonetarySanctionAmount |
MonetarySanctionAmount |
SanctionMonetaryAmount |
The amount ($US) of the financial punishment. |
Level - Sanction |
| mMonetaryAmountSuspended |
MonetarySanctionAmountSuspended |
SuspendedMonetaryAmount |
The $US amount the commander decided to suspend (may be any portion up to all of the monetary sanction). |
Level - Sanction |
| lSanctionDuration |
SanctionDuration |
SanctionDurationQty |
The length of time as an integer for the punishment. Units are needed for this to make sense. |
Level - Sanction |
| vsSuspendedConditions |
SuspendedConditions |
SuspenseConditions |
The conditions of the suspension, as entered by the commander. This is a free text entry, not a pick list. Up to 256 characters may be entered. |
Level - Sanction |
| lSuspendedConditionDuration |
SuspendedDuration |
SuspenseDurationQty |
The length of time as an integer for the suspended sanction. Units are needed for this to make sense. |
Level - Sanction |
| dtSuspenseDate |
SuspendedPeriod |
DateSuspended |
The date the commander decided to suspend the sanction. |
Level - Sanction |
| CaseId |
|
|
A join condition to help ASPTF with normalized tables. |
|
| IncId |
|
|
A join condition to help ASPTF with normalized tables. |
|
| OffID |
|
|
A join condition to help ASPTF with normalized tables. |
|
| InstId |
|
|
Join condition. The instance ID is a unique number assigned to instances in ACI2. There may be more than one instance ID number for each offense in ACI2. For example, two instances of a single office (e.g., assault) might appear in ACI2 for the same person who is a subject of both instances, but with two different victims. That is John hit Mary and John hit Susan are two different counts of the same offense. The Instance ID Number is reported to the requester to speed communication and coordination if there are questions about results. The instance ID number is always and only for one specific set of four elements of data: offense, subject, victim, and investigative finding. This number is unique for each instance in the ACI2 database. |
|
| EntityID |
|
|
A unique number assigned to entities in ACI2. There may be more than one entity ID number for each found SSN. For example, the same SSN might appear in ACI2 for the same person who appears in two different cases. The Entity ID Number is reported to the requester to speed communication and coordination if there are questions about results. Join condition |
|
| ReferralID |
|
|
A join condition to help ASPTF with normalized tables. |
|
| SubjID |
|
|
Same as the EntityID, but labeled for easy reading in context |
|
| VictID |
|
|
Same as the EntityID, but labeled for easy reading in context |
|