| This tab, 1.Cover Letter, describes the information in tab 2 of this document. |
|
|
|
| Tab |
|
Description |
| 2.CIMS_ASCRC-USAPHC(Prov) 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 |
Army STARRS (or USAPHC(Prov)) Approval |
User has accepted this as a valid element for their use-drop down list-Yes or No |
| H |
Army STARRS (or USAPHC(Prov)) SP2Delta |
Date the data element requested in Spiral-2. This will help in revising your existing extract routines |
| I |
FieldType |
This is the data type. |
| J |
Nullability |
This is the Nullability condition |
| K |
Primary Key |
Indicator if data element is a primary key (PK) or foreign key (FK) in this table |
| L |
Title |
Data Element Name |
| M |
Desc |
Dictionary meaning of the data element and enumerated values if applicable |
| N |
Values |
Information on values the element may have |
| O |
Notes |
Notes concerning the element |
| P |
FDM Comments |
Please add any comments that will help us understand the output extract. |
| Q |
ADS Comment |
Please add any comments on authoritativeness |
| R |
Code Table Reference |
Reference to code table. |
| FieldName |
PII/HIPAA Sensitive |
USAPHC (Prov) Approval |
USAPHC (Prov) SP2Delta |
FieldType |
Desc |
Notes |
| Year |
|
Yes |
3/9/2010 |
char(4) |
The year in which the report of investigation (ROI) was initiated. |
tblCase.vsCal_Yr |
| ROI |
|
Yes |
3/9/2010 |
char(5) |
The number of the Report of Investigation. This number is not unique. See CaseNumber. |
tblCase.vsROI_Seq_no |
| CaseNumber |
|
Yes |
3/9/2010 |
char(16) |
The number of the case containing the report of investigation. Unique at the case level. |
tblCase.vsCaseNumber |
| ReportDate |
|
Yes |
3/9/2010 |
char(8) |
The date of the final report of investigation (if entered) - see ROIEnd |
tblCase.dtReportDate |
| IncStart |
|
Yes |
3/9/2010 |
char(8) |
The date an incident began. Incidents describe the general date/time period and location of offenses. There may be more than one incident per case. |
tblCase.dtDate_incdnt_start |
| IncEnd |
|
Yes |
3/9/2010 |
char(8) |
The date an incident period ended. |
tblCase.dtDate_incdnt_end |
| ROIStart |
|
Yes |
3/9/2010 |
char(8) |
The date the initial report of investigation was reported. |
tblCase.dtOpenDate |
| ROIEnd |
|
Yes |
3/9/2010 |
char(8) |
The date the final report of investigation was reported. |
tblCase.dtCloseDate |
| Primary |
|
Yes |
3/9/2010 |
char(1) |
Indicator of primary offense. Y means this is the offense for which the most severe potential punishment may be imposed as determined by the Uniform Code of Military Justice (UCMJ) or other applicable authority. N means that some other offense is primary for the case. |
Constructed |
| OffCode |
|
Yes |
3/9/2010 |
char(7) |
Offense Code. See Army Regulation 195-45, Military Police Law Enforcement Reporting. There may be more than one offense per incident. There may be more than one offense per incident. |
tblCase.vsPrimaryOffense_cd |
| Offense Description |
|
Yes |
3/9/2010 |
char(100) |
Offense description. Descriptions from ASCRC may vary from those found in AR 190-45. |
tblOffense.vsOffns_desc |
| Name |
Yes |
Yes |
3/9/2010 |
char(100) |
Name |
tblPerson.vsName |
| SSN |
DI |
Yes |
3/9/2010 |
char(9) |
Social Security Number |
tblPerson.vsSSN |
| DOB |
|
Yes |
3/9/2010 |
char(8) |
Date of birth |
tblPerson.dtDOB |
| Year |
|
Yes |
3/9/2010 |
char(4) |
The year in which the report of investigation (ROI) was initiated. |
tblCase.vsCal_Yr |
| ROI |
|
Yes |
3/9/2010 |
char(5) |
The number of the Report of Investigatoin. This number is not unique, See CaseNumber |
tblCase.vsROI_Seq_no |
| CaseNumber |
|
Yes |
3/9/2010 |
char(16) |
The number of the case contaning the report of investigation. Unique at the case level. |
tblCase.vsCaseNumber |
| PersonID |
|
Yes |
3/9/2010 |
char(11) |
A number in the database used to refer to persons without using name or ssn. Unique at person level. |
tblPerson.lPerson |
| SV |
|
Yes |
3/9/2010 |
char(1) |
Indicator of the person's role in the case. S= Subject. V = Victim. |
tblPerson.vsSvb_flag |
| Person_Type_cd |
|
Yes |
3/9/2010 |
char(10) |
Person type category code |
tblPerson.vsPrsn_type_cd |
| Person_Type_Description |
|
Yes |
3/9/2010 |
char(256) |
Person type category description |
tblPrsn_type.vsPrsn_type_desc |
| Grade_cd |
DI |
Yes |
3/9/2010 |
char(10) |
Grade code |
tblPerson.vsGrd_cd |
| Grade Description |
DI |
Yes |
3/9/2010 |
char(256) |
Grade description |
tblGrade.vsGrd_desc |
| Mcac_cd |
|
Yes |
3/9/2010 |
char(10) |
Major Command Activity Code |
tblPerson.vsMcac |
| PersonUnitDescription |
|
Yes |
3/9/2010 |
char(256) |
MCAC description (do not confuse with CID unit) |
tblMcac.vsMcac_name |
| Sex |
|
Yes |
3/9/2010 |
char(1) |
Sex, M or F |
.vsSex_cd |
| Race_cd |
|
Yes |
3/9/2010 |
char(10) |
Race code |
tblPerson.vsRace_cd |
| Race |
|
Yes |
3/9/2010 |
char(256) |
Race category |
tblRace.vsRace_desc |
| Ethnic_cd |
|
Yes |
3/9/2010 |
char(10) |
Ethnicity code |
tblPerson.vsEthnic_cd |
| Ethnicity |
|
Yes |
3/9/2010 |
char(256) |
Ethnicity category |
tblEthnic.vsEethnic_desc |