| This tab, 1.Cover Letter, describes the information in tab 2 of this document. | ||
| Tab | Description | |
| 2.TMDS-STARRS 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. |
| Source | Source Tab Ord | SourceTable | Source Field Ord | FieldName | PII/HIPAA Sensitive | USAPHC(P) | Army STARRS Approval | FieldType | Nullability | Primary Key | Title | Desc | Values | Notes | FDM Comments | ADS Comment | Code Table Reference | Question | Response | Potential Source | Field Requires Table? | Still Need the Code Table? | Check Again to Drop Field? | BL Notes |
| TMDS | 1 | PEM | 1 | PEM_ID | Yes | Yes | NUMBER | N | PK | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 1 | PEM | 2 | PEOPLE_ID | Yes | Yes | NUMBER | N | FK to PEOPLE | People Identifier | no | |||||||||||||
| TMDS | 1 | PEM | 3 | MTFID | Yes | Yes | VARCHAR2(80) | Y | Military Treatment Facility Identifier | Is this the DMIS ID? If not, can it be crosswalked to it? It seems like a long field (Varchar2(80)) | This is not the DMISID. This is the TMDS System ID for a MTF. This value can be a DMISID id if the record is from TC2, but if the record is from AHLTA-T the values are UICs. | yes | yes | |||||||||||
| TMDS | 1 | PEM | 4 | CASE_ID | Yes | Yes | VARCHAR2(120) | Y | Case Identifier | Uniqe combination of several values provided in the PEM encounter to determine if this encounter is unique or a duplicate. | no | if its unique its not a lookup | ||||||||||||
| TMDS | 1 | PEM | 5 | ORIGINAL_DATE | No | No | DATE | Y | Original Date | This is the date the record was created. | Is this the date the record was created? | Yes | no | |||||||||||
| TMDS | 1 | PEM | 6 | PROGNOSIS | Yes | Yes | VARCHAR2(50) | Y | Medical Prognosis | Free Text | This is a free text field. | Is there a lookup table of values or free text? | This is a free text field | no | ||||||||||
| TMDS | 1 | PEM | 7 | DNBI_ID | No | No | NUMBER | Y | DNBI identifier | What is this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 8 | MECHANISM_ID | Yes | Yes | NUMBER | Y | Mechanism ID | ID # that corresponds to pt disposition | See PVList.PVLISTID | What are the criteria used to determine if this field should be filled in with something? | We do not know when the sending system decides to provide this value. Not al sending systems have this field and it appears to be randomly populated. | yes | no | |||||||||
| TMDS | 1 | PEM | 9 | DISPOSITION_ID | Yes | Yes | NUMBER | Y | Disposition Identifier | yes | yes | Not too sure… shows up a few times so it may be a foreign key? | ||||||||||||
| TMDS | 1 | PEM | 10 | INITIAL_VISIT_IND | Yes | Yes | CHAR(1) | Y | Initial Visit Indicator | N = Follow Up, Y = Initial Visit | How does a visit get to be an "initial" visit - first time at MTF for that SSN? | This is a business rule for a TC2 or AHLTA-T. It is the initial visit for a specific problem. Any subsequent visit is a Follo Up. A patient can have multiple Initial Visits for multiple distinct problems at the same MTF ( NOTE: This is the TMDS developer understanding of how this value is set by AHLTA-T) | no | |||||||||||
| TMDS | 1 | PEM | 11 | REPORT_DATE | No | No | DATE | Y | Last Report Date | This is the date on which the data source file was created ( AHLTA-T, TC2 etc.) | no | |||||||||||||
| TMDS | 1 | PEM | 12 | SUBJECTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Subjective description | no | |||||||||||||
| TMDS | 1 | PEM | 13 | OBJECTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Objective description | no | |||||||||||||
| TMDS | 1 | PEM | 14 | ASSESSMENT | Yes | Yes | No | VARCHAR2(4000) | Y | Medical assessment | no | |||||||||||||
| TMDS | 1 | PEM | 15 | PLAN_OF_CARE | Yes | Yes | No | VARCHAR2(4000) | Y | Treatment plan | no | |||||||||||||
| TMDS | 1 | PEM | 16 | PREVENTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Preventive | no | |||||||||||||
| TMDS | 1 | PEM | 17 | FILE_NAME | No | No | VARCHAR2(100) | Y | Name of file | Is this the name of your source file? We probably don't need this unless TMDS wants us to have it for troubleshooting. | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 18 | DATA_SOURCE | Yes | Yes | VARCHAR2(50) | Y | Data source | This field contains the name of the data source that provided the specific medical information. Example: AHLTA-T, AHLTA-M, TC2, SAMS8, SAMS9, GEMS etc, | no | |||||||||||||
| TMDS | 1 | PEM | 19 | ENCOUNTER_TYPE | No | No | VARCHAR2(50) | Y | Encounter type | This is not a look up table but we've seen values such as ROUTN, ACUTE | Is this a lookup table? | This is not a look up table but we've seen values such as ROUTN, ACUTE | no | |||||||||||
| TMDS | 1 | PEM | 20 | ENCOUNTER_DATE | Yes | Yes | DATE | Y | Encounter date | no | ||||||||||||||
| TMDS | 1 | PEM | 21 | KIN_NOTIFIED | No | Yes | CHAR(1) | Y | Kin Notified | Code to determine if next-of-kin has been notified. | yes | yes | ||||||||||||
| TMDS | 1 | PEM | 22 | OUT_PATIENT_IND | Yes | Yes | CHAR(1) | Y | Outpatient Indicator | Y = OUTPATIENT N = INPATIENT |
How is this field coded? | Y = OUTPATIENT N = INPATIENT |
no | |||||||||||
| TMDS | 1 | PEM | 23 | EST_DAY | Yes | Yes | NUMBER | Y | Estimated Day | Please define this field-provide algorithm if available | This is an AHLTA-T field, I belive this is the Estimated Days of Lite Duty when patient is discharged as QUARTERS or LIGHT DUTY ( NOTE: AHLTA_T developer to confirm) | AHLTA-T | no | |||||||||||
| TMDS | 1 | PEM | 24 | LITE_DAYS | Yes | Yes | NUMBER | Y | Lite Days | Please define this field-provide algorithm if available | Number of Days when Lite Duty is assigned | no | ||||||||||||
| TMDS | 1 | PEM | 25 | LOSS_DAYS | Yes | Yes | NUMBER | Y | Loss Days | Please define this field-provide algorithm if available | Days of work missed ( NOTE: TMDS developer's understanding of AHLTA-T fields) | no | ||||||||||||
| TMDS | 1 | PEM | 26 | INJURY_TYPE | Yes | Yes | NUMBER | Y | Injury Type | Type of injury that occurred to patient | See PVList.PVLISTID | Please provide algorithm used to determine if this field gets populated. | We do not have an algorithm to determine if this field is populated or not. | yes | no | |||||||||
| TMDS | 1 | PEM | 27 | PROVIDER | No | No | VARCHAR2(250) | Y | Provider Name | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 1 | PEM | 28 | TOBACCO_USE | Yes | Yes | VARCHAR2(4000) | Y | Tobacco use narrative | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 1 | PEM | 29 | ALCOHOL_USE | Yes | Yes | VARCHAR2(4000) | Y | Alcohol use narrative | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 1 | PEM | 30 | CURRENT_MEDS | Yes | Yes | VARCHAR2(4000) | Y | Current medications narrative | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 1 | PEM | 31 | DISP_DURATION | Yes | Yes | NUMBER | Y | Number of days of duration | Duration of what? How is this field filled in? | DISPOSITION DURATION. For example, if the disposition is LIMITED DUTY , the number of days this disposition is in effect. | no | ||||||||||||
| TMDS | 1 | PEM | 32 | DISP_DUTY_LIMITATIONS | Yes | Yes | VARCHAR2(4000) | Y | Limitations defined during disposition | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 1 | PEM | 33 | OTHER_DISP | Yes | Yes | VARCHAR2(100) | Y | Narrative of other disposition | no | ||||||||||||||
| TMDS | 1 | PEM | 34 | REF_LOC | Yes | Yes | VARCHAR2(100) | Y | Referred Location | Location Where the Patient was Referred or Evacuated | Free Text | Is this categorized at all, or just free text? | This is free text field. | no | ||||||||||
| TMDS | 1 | PEM | 35 | REF_MODE | No | No | VARCHAR2(80) | Y | Mode of Transport | Is this categorized at all, or just free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 36 | CHIEF_COMPLAINT | Yes | Yes | No | VARCHAR2(4000) | Y | Chief Complaint | Main Complaint from the patient | no | ||||||||||||
| TMDS | 1 | PEM | 37 | ONSET_DATE | Yes | Yes | DATE | Y | Onset Date | The date symptoms started to occur | no | |||||||||||||
| TMDS | 1 | PEM | 38 | VIS_IND | No | No | CHAR(1) | Y | VIS Indicator | This field appears to be populated by SAMS8 ( Navy) data source only. Visit Indicator. | no | |||||||||||||
| TMDS | 1 | PEM | 39 | HEIGHT | No | Yes | VARCHAR2(32) | Y | Patient's Height | How is this coded? Are units assumed? | feet and inches, sometimes in inches only. There is an option for CM as well. | no | ||||||||||||
| TMDS | 1 | PEM | 40 | WEIGHT | No | Yes | VARCHAR2(32) | Y | Patient's Weight | How is this coded? Are units assumed? | lbs, but there is an option for kg. | no | ||||||||||||
| TMDS | 1 | PEM | 41 | EM_CODE | Yes | Yes | VARCHAR2(10) | Y | CPT Evaluation and Management Code | Please define this field. Is there a code list? | I am not sure what this | yes | yes | |||||||||||
| TMDS | 1 | PEM | 42 | MEPRS_CODE | Yes | Yes | VARCHAR2(10) | Y | Medical Expense Performance and Reporting System Code | Please define this field. Is there a code list? | Medical Expense and Performance Reporting System (MEPRS) codes are standard list of MHS codes. | yes | yes | |||||||||||
| TMDS | 1 | PEM | 43 | PEM_TIMESTAMP | No | No | DATE | Y | PEM creation date and time | This value may not be of interest to ArmySTARRS, this is the actual timestamp when the record was inserted in TMDS DB. It cannot be used for sequential analysis. | Will we need this to keep subsequently modified records in order? | This value may not be of interest to ArmySTARRS, this is the actual timestamp when the record was inserted in TMDS DB. It cannot be used for sequential analysis. | no | |||||||||||
| TMDS | 1 | PEM | 44 | DIAGNOSIS_SURVEILLABLE_IND | No | No | CHAR(1) | Y | Diagnosis Surveillance Indicator | What does this mean, and how is it coded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 45 | LABRTF | Yes | No | No | VARCHAR2(4000) | Y | Laboratory RTF | This is a legacy field which is not in use.TMDS recommendation is to eliminate it from feed. | no | ||||||||||||
| TMDS | 1 | PEM | 46 | RADRTF | Yes | No | No | VARCHAR2(4000) | Y | Radiology RTF | This is a legacy field which is not in use.TMDS recommendation is to eliminate it from feed. | no | ||||||||||||
| TMDS | 1 | PEM | 47 | ITEMS_DISCUSSED | No | No | VARCHAR2(30) | Y | Items Discussed | Free Text | This is a free text field. | Lookup table or free field? | It’s a free text field | no | ||||||||||
| TMDS | 1 | PEM | 48 | FOLLOWUP_TIME | No | Yes | VARCHAR2(50) | Y | Next Follow Up Time | We receive this element from AHLTA-T system. We believe it reflects the time and date of the follow up appointment. | 1. What does this element tell us? Does it have anything to do with recommended f/u care or treatment? 2. Is this free text? If not, how is it coded? | 1. We receive this element from AHLTA-T system. We believe it reflects the time and date of the follow up appointment. 2. [NO ANSWER] | AHLTA-T | no | ||||||||||
| TMDS | 1 | PEM | 49 | FOLLOWUP_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Follow Up Comments | no | |||||||||||||
| TMDS | 1 | PEM | 50 | DISCUSSED_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Discussion Comments | no | |||||||||||||
| TMDS | 1 | PEM | 51 | CHRONICITY_IND | Yes | Yes | CHAR(1) | Y | Chronic Indicator | Please define this field-provide algorithm if available | This appears to be a legacy field which is not populated by AHLTA-T and TC2 systems. | yes | yes | yes | ||||||||||
| TMDS | 1 | PEM | 52 | SENSITIVITY_LEVEL | Yes | Yes | NUMBER | Y | Sensitivity Level | What does this mean? What levels are there, and what do they mean? | This is an AHLTA-T field. TMDS does not have the complete list of Sensitivity Levels and what they mean, we store this information as provided by source system. | AHLTA-T | yes | yes | ||||||||||
| TMDS | 1 | PEM | 53 | MAPPED_DNBI_CATEGORY | No | No | VARCHAR2(40) | Y | DNBI Category Mapped To This PEM | What does this mean, and how is it coded? | This is the TMDS system mapping of an ICD9 code to a DNBI Category. The AHLTA-T system sends TMDS the ICD9 and DNBI Category, but sometimes the ICD9 code does not map to the provided DNBI Category. | no | ||||||||||||
| TMDS | 1 | PEM | 54 | AGE | Yes | Yes | NUMBER | Y | Age Of Patient | no | ||||||||||||||
| TMDS | 1 | PEM | 55 | AREA_OF_OPERATION_ID | Yes | Yes | NUMBER | Y | Area Of Operation Identifier | What does "area of operation" refer to? Is there a picklist for this field - or a definition of each numerical level? | TMDS can provide you with the lsit of AORs. We have them in a separate table. This is just JPTA field only. | yes | yes | |||||||||||
| TMDS | 1 | PEM | 56 | VIP_TYPE_ID | No | No | NUMBER | Y | VIP Type Identifier | What is VIP Type? Is there a picklist for this field - or a definition of each numerical level? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 57 | PATIENT_CONDITION_ID | Yes | Yes | NUMBER | Y | Patient Condition Identifier | See PVList.PVLISTID | Is this coded on all PEMs, or just the ones from JPTA? | Just JPTA | yes | no | ||||||||||
| TMDS | 1 | PEM | 58 | AMPUTATION_CAUSE_ID | Yes | Yes | NUMBER | Y | Amputation Cause Identifier | Is the picklist for this possibly in PVLIST somehow? | Yes | yes | yes | |||||||||||
| TMDS | 1 | PEM | 59 | BLOOD_TRANS_IND | Yes | Yes | CHAR(1) | Y | Blood Transfusion Indicator | How is this coded? | This field is no longer used. JPTA legacy field. | yes | yes | yes | ||||||||||
| TMDS | 1 | PEM | 60 | ORIGINAL_DISPOSITION_ID | No | No | NUMBER | Y | Original Disposition Identifier | What does this field mean? Is this the first disposition? If so, is there a picklist? | The original value of the disposition as provided by the source system. | no | ||||||||||||
| TMDS | 1 | PEM | 61 | DISPOSITION_DATE | Yes | Yes | DATE | Y | Disposition Date | This date applies to PEM.DISPOSITION_ID | Is this the date for the PEM.DISPOSITION_ID you mentioned in your e-mail, or does it go with the ORIGINAL_DISPOSITION_ID above? | This date applies to PEM.DISPOSITION_ID | no | |||||||||||
| TMDS | 1 | PEM | 62 | PROVIDER_ID | Yes | Yes | NUMBER | Y | Medical Provider Identifier | The PROVIDER_ID is a FK to the PEM_PROVIDER table. Please let us know if you want to receive any elemens from the PEM_PROVIDER table so we can include them in the extract. | 1. I don't believe A-STARRS is permitted to receive sensitive data like provider names, phone numbers, etc. This is currently in the "PEM_Provider" look up table. If the sensitive data is removed from th pick list, it is unclear what we would get from this element (e.g., specialty of provider?) 2. PEM_PROVIDER hooks on here. Can you also patch in SPECIALTY from that table, and give me a way to decode the SPECIALTY code? | 1. The PROVIDER_ID is a FK to the PEM_PROVIDER table. Please let us know if you want to receive any elemens from the PEM_PROVIDER table so we can include them in the extract. 2. [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 63 | DISCHARGE_PROVIDER_ID | No | No | NUMBER | Y | Discharge Provider Identifier | PEM_PROVIDER hooks on here. Can you also patch in SPECIALTY from that table, and give me a way to decode the SPECIALTY code? | The specialty/MOS is a standard list of codes for each service. We can provide you with the list we have. | no | ||||||||||||
| TMDS | 1 | PEM | 64 | OUTPATIENT_LOCATION | Yes | Yes | VARCHAR2(100) | Y | Outpatient Location | Free Text | Is this free text? If not, how is it coded? | Yes, free text | no | |||||||||||
| TMDS | 1 | PEM | 65 | OPEN_IND | No | No | CHAR(1) | Y | Open Indicator | This applies to TMDS records only, which are OPEN until discharded. TMDS does not have the capability to sign a record as in AHLTA-T. This information may not be relevant to ArmySTARRS. A record is "open" until a dispositions and disposition date are provided, then the records becomes "closed". This is an internal TMDS DB logic for several reports and this field is not relevant to ArmySTARRS. | 1. Record open? Not signed by provider? 2. Under what conditions are records "discarded" from TMDS? | 1. This applies to TMDS records only, which are OPEN until discharded. TMDS does not have the capability to sign a record as in AHLTA-T. This information may not be relevant to ArmySTARRS. 2. A record is "open" until a dispositions and disposition date are provided, then the records becomes "closed". This is an internal TMDS DB logic for several reports and this field is not relevant to ArmySTARRS. | no | |||||||||||
| TMDS | 1 | PEM | 66 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | This is internal TMDS value and is not of intereset to ArmySTARRS. It cannot be used to keep records in order. | Do we need these to keep records in order? | This is internal TMDS value and is not of intereset to ArmySTARRS. It cannot be used to keep records in order. | no | |||||||||||
| TMDS | 1 | PEM | 67 | SRC_UNIQUE_ID | No | No | VARCHAR2(120) | Y | SRC Unique Identifier | This is the Encounter Number value provided by AHLTA-T/M files only. | SRC=Soldier Readiness Center? | This is the Encounter Number value provided by AHLTA-T/M files only | no | |||||||||||
| TMDS | 1 | PEM | 68 | SRC_ENCOUNTER_ID | No | No | NUMBER | Y | Source Encounter Identifier | This is the Appoiintment Id value provided by AHLTA-T/M files only. | no | |||||||||||||
| TMDS | 1 | PEM | 69 | SRC_MTFID | No | No | VARCHAR2(80) | Y | SRC MTF Identifier | This is the FaciliyNCID value provided by AHLTA-T/M only. | no | |||||||||||||
| TMDS | 1 | PEM | 70 | SIGNED_DATE | No | No | DATE | Y | Signed Date | What date does this indicate? | when provider signed the encounter | no | ||||||||||||
| TMDS | 1 | PEM | 71 | SENSITIVE_IND | No | No | CHAR(1) | Y | Sensitive Indicator | Does the record contain sensitive information. 'Y' for sensitive, 'N' for non-sensitive | What does "sensitive" mean? | At provider's discretion, the record can be tagged as sensitive if it contains HIV, Behavioural Health, Death Related disposition or any other similar informaiton. | no | |||||||||||
| TMDS | 1 | PEM | 72 | TRAN_UNLICENSED_BLOOD_IND | Yes | Yes | CHAR(1) | Y | Transfused Unlicensed Blood Indicator | Yes, No | This DB element is not used. It is intended to denote whether the blood transfused was FDA or non-FDA. TMDS now has a new Blood Module capability which will capture this information. NOTE: Blood module is not deployed to production system at present. | What does this element tell us? | This DB element is not used. It is intended to denote whether the blood transfused was FDA or non-FDA. TMDS now has a new Blood Module capability which will capture this information. NOTE: Blood module is not deployed to production system at present. | no | yes | |||||||||
| TMDS | 1 | PEM | 73 | WARD_BILLETING_ID | No | No | NUMBER | Y | Ward Billeting Identifier | What does this field mean? | JPTA legacy field. | no | ||||||||||||
| TMDS | 1 | PEM | 74 | ROOM_NUMBER | No | No | VARCHAR2(100) | Y | Room Number | Room number in ward_billeting_id indicating patient's location | no | |||||||||||||
| TMDS | 1 | PEM | 75 | INCIDENT_ID | No | No | NUMBER | Y | Incident Identifier |
This is an internal TMDS DB value intended for grouping records to the same incident. This value is being phased out and is no longer in use. | 1. What does this element tell us? 2. Do we need this to hook onto another table with INCIDENT_ID in it? | 1. This is an internal TMDS DB value intended for grouping records to the same incident. This value is being phased out and is no longer in use. 2. [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 76 | REACTIVATE_USER_ID | No | No | NUMBER | Y | Reactivate User Identifier | What does this mean? Do we need it? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 77 | REACTIVATE_DATE | No | No | DATE | Y | Reactivate Date | What is reactivated? What's this about? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 78 | NEW_ORIGINAL_DISPOSITION_ID | No | No | NUMBER | Y | New Originial Disposition ID | The original disposition selected from the UI that user has selected, references to XREF_JPTA_L3_DISPCODE.DISP_ID | What dispositions are there? I have seen 3 so far. What do they all mean? This looks like one I don't want, but which ones do I want? | [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 79 | TRANSFER_MTFID | No | No | VARCHAR2(80) | Y | Transfer MTFID | Transfer MTFID of a JPTA patient | Transfer from MTF, or transfer to MTF? Can MTF be decoded from tables? | [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 80 | TRANSFER_DESC | No | No | VARCHAR2(255) | Y | Transfer Description | Transfer location of a JPTA patient | What sort of "location"? Is this categorized or free text? | [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 81 | ORIGINAL_GENDER | No | No | VARCHAR2(1) | Y | Original Gender | Gender received from AHLTA-T. | no | |||||||||||||
| TMDS | 1 | PEM | 82 | WHEN_COSIGNED | No | No | DATE | Y | When Co-Signed NCID | Date of co-signed NCID | What does this date mean? | [NO ANSWER] | no | |||||||||||
| TMDS | 1 | PEM | 83 | WHO_COSIGNED_NCID | No | No | NUMBER | Y | Who Co-Signed NCID | What kind of person is this - a patient, or a provider? | [NO ANSWER] | no | ||||||||||||
| TMDS | 1 | PEM | 84 | COSIGNER_NCID | No | No | NUMBER | Y | Co-signer NCID | What kind of person is this - a patient, or a provider? | [NO ANSWER] | no | ||||||||||||
| TMDS | 2 | PEM_ACCIDENT | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | I assume this is the FK back to PEM. Do PEM records have a one to many relationship with this table, or a one-to-one? Under what circumstances is a record added to this table? | FK to PEM. Record is added if it was submitted as part of the encounter. There is one PEM ACCIDENT per PEM. The PEM_ACCIDENT table is not used by AHLTA-T and TC2. This table was used by GEMS (Airforce Patient Encounter Module) and SAMS ( theNavy's version). These modules are being phased out. | no | yes | ||||||||||
| TMDS | 2 | PEM_ACCIDENT | 2 | INC_DATE | Yes | Yes | DATE | Y | Incident Date | Is this the date of the injury, or some other date? | incident date | no | ||||||||||||
| TMDS | 2 | PEM_ACCIDENT | 3 | INC_LOCATION | Yes | Yes | VARCHAR2(100) | Y | Incident Location | Free Text | Is this categorized at all, or just free text? | free text of the location | no | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 4 | INC_CIRCUMSTANCE | Yes | Yes | No | VARCHAR2(4000) | Y | Incident Circumstance | no | |||||||||||||
| TMDS | 2 | PEM_ACCIDENT | 5 | ON_OFF_DUTY | Yes | Yes | NUMBER | Y | On or Off Duty Flag | 1 = On Duty, 0 = Off Duty | Please provide coding for this field. | 1 on duty, 0 off | no | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 6 | AFLOAT | Yes | Yes | NUMBER | Y | Afloat | 1 = Yes, 0 = No | Please provide definition and coding for this field. | 1-yes, 0-no | no | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 7 | SAFTEY_HAZARD | Yes | Yes | CHAR(1) | Y | Safety Hazard | Y, N | Please provide definition and coding for this field. | Y,N | no | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 8 | MOTOR_VEHICLE_BI | Yes | Yes | NUMBER | Y | Motor Vehicle BI | Please provide definition and coding for this field. | TBD | yes | yes | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 9 | DISABLED | Yes | Yes | CHAR(1) | Y | Disabled | Y, N | Please provide definition and coding for this field. | Y,N | no | |||||||||||
| TMDS | 2 | PEM_ACCIDENT | 10 | COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | PEM Accident Comments | no | |||||||||||||
| TMDS | 2 | PEM_ACCIDENT | 11 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 1 | ID | Yes | Yes | NUMBER | N | PK | Identifier | Internal DB value in support of referential integrity. This table contain Notes from AHLTA-T/M files only. The JPTA notes are stored in TMDS_PATIENT_NOTES table. | no | ||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 2 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 3 | PEM_INPATIENT_DETAIL_ID | Yes | Yes | NUMBER | Y | PEM Inpatient Detail Identifier | no | I think this is a foreign key? | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 4 | AUDIT_ID | No | No | NUMBER | N | Audit Identifier | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 5 | TITLE | Yes | Yes | VARCHAR2(80) | Y | Title | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 6 | NOTE_TEXT | Yes | Yes | No | CLOB | N | Free text field for note text | no | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 7 | SRC_UNIQUE_ID | No | No | VARCHAR2(120) | Y | SRC Unique Identifier | This is a DB related id provided in the data source files. It does not have medical relevance. | no | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 8 | NOTE_TIMESTAMP | No | No | DATE | Y | Note Timestamp | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 9 | CONTENT_TYPE | Yes | Yes | VARCHAR2(100) | N | Content Type | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 10 | NOTE_PTR | No | No | BFILE | Y | Note Pointer | Pointer to file outside of DB related to note | no | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 11 | FACILITY_NOTE_ENTERED | Yes | Yes | VARCHAR2(80) | Y | Facility Note Entered | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 12 | UI_UPLOADED | No | No | CHAR(1) | N | UI Uploaded | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 13 | DESCRIPTION | Yes | Yes | VARCHAR2(250) | Y | Description | no | ||||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 14 | FILE_NAME | No | No | VARCHAR2(200) | Y | File Name | Name of file | no | |||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 15 | CARE_STATUS_ID | Yes | Yes | NUMBER | Y | Care Status Identifier | See XREF_CARE_STATUS.ID | yes | no | ||||||||||||
| TMDS | 3 | PEM_APPEND_NOTES | 16 | PROC_HX_STATUS | Yes | Yes | CHAR(1) | N | Procedure HX Status | yes | yes | |||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 1 | PEM_ID | No | No | NUMBER | N | FK to PEM | Patient Encounter Identifier | This is an obsolete DB object that needs to be removed from TMDS DB and this feed. | no | ||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 2 | NOTE_ID | No | No | NUMBER | N | PK | Note Identifier | no | |||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 3 | NOTE_TYPE | No | No | VARCHAR2(40) | Y | Note Type | no | ||||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 4 | NOTE_DATE | No | No | DATE | Y | Date Of Note | no | ||||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 5 | POC_FACILITY | No | No | NUMBER | Y | Point Of Contact Facility | no | ||||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 6 | CLINICIAN | No | No | VARCHAR2(50) | Y | Medical Clinician | no | ||||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 7 | NOTE_TEXT | Yes | No | No | VARCHAR2(4000) | Y | Detailed Note Text | no | |||||||||||||
| TMDS | 4 | PEM_CLINICAL_NOTES | 8 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 5 | PEM_CPT4 | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 5 | PEM_CPT4 | 2 | CPT4_CODE | Yes | Yes | VARCHAR2(10) | N | Current Procedure Terminology Code | yes | yes | |||||||||||||
| TMDS | 5 | PEM_CPT4 | 3 | MEDCIN_ID | Yes | Yes | NUMBER | Y | MEDCIN Identifier | http://en.wikipedia.org/wiki/MEDCIN | Assuming MEDCIN picklist hooks on here (FK to MEDCIN picklist). What is MEDCIN coding? | http://en.wikipedia.org/wiki/MEDCIN | no | |||||||||||
| TMDS | 5 | PEM_CPT4 | 4 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | This is internal TMDS value and is not of intereset to ArmySTARRS. It cannot be used to keep records in order. | This would allow us to see if the code changed? | This is internal TMDS value and is not of intereset to ArmySTARRS. It cannot be used to keep records in order. | no | |||||||||||
| TMDS | 6 | PEM_DISP_HIST | 1 | PEM_ID | No | No | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 2 | PEM_DISP_HIST_ID | No | No | NUMBER | Y | PEM Disposition History Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 3 | MTFID | No | No | VARCHAR2(80) | Y | Military Treatment Facility Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 4 | ORIGINAL_DISPOSITION_ID | No | No | NUMBER | Y | Original Disposition Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 5 | DISPOSITION_ID | No | No | NUMBER | Y | Disposition Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 6 | LOCATION | No | No | VARCHAR2(100) | Y | Unit Location | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 7 | DISP_HIST_TIMESTAMP | No | No | DATE | Y | Disposition History Timestamp | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 8 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 9 | WARD_BILLETING_ID | No | No | NUMBER | Y | Ward Billeting Identifier | no | ||||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 10 | TRANSFER_MTFID | No | No | VARCHAR2(80) | Y | Transfer MTFID | The MTFID the patient was transferred to | no | |||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 11 | TRANSFER_DESC | No | No | VARCHAR2(250) | Y | Transfer Description | The description of the facility the patient was transferred to when MTFID does not exist | no | |||||||||||||
| TMDS | 6 | PEM_DISP_HIST | 12 | NEW_ORIGINAL_DISPOSITION_ID | No | No | NUMBER | Y | New Originial Disposition ID | The original disposition selected from the UI that user has selected, references to XREF_JPTA_L3_DISPCODE.DISP_ID | no | |||||||||||||
| TMDS | 7 | PEM_ENABLING_CARE | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | Assume this is FK to PEM table | [NO ANSWER] | no | |||||||||||
| TMDS | 7 | PEM_ENABLING_CARE | 2 | ENABLING_CARE_TYPE_ID | Yes | Yes | NUMBER | N | Enabling Care Type Identifier | See XREF_ENABLING_CARE_TYPES.ID | Please provide doco of algorithm you use to classify into enabling types. What types of PEM's get records in this table? | JPTA legacy field. | yes | no | ||||||||||
| TMDS | 7 | PEM_ENABLING_CARE | 3 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 8 | PEM_ICD9 | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 8 | PEM_ICD9 | 2 | PEM_ICD9_ID | Yes | Yes | NUMBER | Y | PEM ICD9 Identifier | yes | yes | |||||||||||||
| TMDS | 8 | PEM_ICD9 | 3 | ICD9_CODE | Yes | Yes | VARCHAR2(32) | Y | ICD9 Code | yes | yes | |||||||||||||
| TMDS | 8 | PEM_ICD9 | 4 | ICD9_DIAGNOSIS | Yes | Yes | VARCHAR2(500) | Y | ICD9 Diagnosis | This is not a PII field. It displays the official diagnosis description associated with the ICD9 code. | no | |||||||||||||
| TMDS | 8 | PEM_ICD9 | 5 | PRIMARY_DIAGNOSIS_IND | Yes | Yes | NUMBER | Y | Primary Diagnosis Indicator | Please explain what the different numbers will mean. How is "primary" selected out of the different diagnoses? Or is this just the order of diagnoses on the PEM? | If a record contains more than one ICD9 code, the first code provided is set as the Primary ICD9 code. | yes | yes | |||||||||||
| TMDS | 8 | PEM_ICD9 | 6 | DESCRIPTION | Yes | Yes | VARCHAR2(1000) | Y | Description | This is not a PII field. It displays the official diagnosis description associated with the ICD9 code. | no | |||||||||||||
| TMDS | 8 | PEM_ICD9 | 7 | MEDCIN_ID | Yes | Yes | NUMBER | Y | MEDCIN Identifier | http://en.wikipedia.org/wiki/MEDCIN | I need to better understand MEDCIN system/picklist. Sample data would be helpful. | MEDCIN is a third party COTS software | no | |||||||||||
| TMDS | 8 | PEM_ICD9 | 8 | GEMS_ID | No | No | VARCHAR2(40) | Y | GEMS Identifier | no | ||||||||||||||
| TMDS | 8 | PEM_ICD9 | 9 | SENSITIVITY_IND | Yes | Yes | CHAR(1) | Y | Sensitivity Indicator | Y = Sensitive, N = Non-Sensitive | Is this coded according to another field of a similar name: "Does the record contain sensitive information. 'Y' for sensitive, 'N' for non-sensitive"? What does sensitive mean? | Yes | no | |||||||||||
| TMDS | 8 | PEM_ICD9 | 10 | ICD93 | No | No | VARCHAR2(4) | Y | ICD93 Code | This value may not be of interest to ArmySTARRS. It is the same value as ICD9_CODE but contains only the 3-digit root code. TMDS recormmendation is to remove this from the feed to ArmySTARRS and provide the ICD9_CODE value only. | Is this the 3-digit root code? | This value may not be of interest to ArmySTARRS. It is the same value as ICD9_CODE but contains only the 3-digit root code. TMDS recommendation is to remove this from the feed to ArmySTARRS and provide the ICD9_CODE value only | no | |||||||||||
| TMDS | 8 | PEM_ICD9 | 11 | ICD95 | No | No | VARCHAR2(7) | Y | ICD95 Code | This value may not be of interest to ArmySTARRS. It is the same value as ICD9_CODE but contains only the 5-digit root code. TMDS recormmendation is to remove this from the feed to ArmySTARRS and provide the ICD9_CODE value only. | Is this the full 5-digit code? How does it differ from ICD9_CODE? | This value may not be of interest to ArmySTARRS. It is the same value as ICD9_CODE but contains only the 5-digit root code. TMDS recommendation is to remove this from the feed to ArmySTARRS and provide the ICD9_CODE value only | no | |||||||||||
| TMDS | 8 | PEM_ICD9 | 12 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 2 | PEM_ICD9_ID | Yes | Yes | NUMBER | N | PEM ICD9 Identifier | yes | yes | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 3 | PEM_INPATIENT_DETAIL_ID | Yes | Yes | NUMBER | Y | PEM Inpatient Detail Identifier | no | I think this is a foreign key? | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 4 | ICD9_CODE | Yes | Yes | VARCHAR2(32) | Y | ICD9 Code | yes | yes | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 5 | ICD9_DIAGNOSIS | Yes | Yes | VARCHAR2(500) | Y | ICD9 Diagnosis | This is not a PII field. It displays the official diagnosis description associated with the ICD9 code. | no | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 6 | PRIMARY_DIAGNOSIS_IND | Yes | Yes | NUMBER | Y | Primary Diagnosis Indicator | yes | yes | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 7 | DESCRIPTION | Yes | Yes | VARCHAR2(1000) | Y | Description | This is not a PII field. It displays the official diagnosis description associated with the ICD9 code. | no | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 8 | MEDCIN_ID | Yes | Yes | NUMBER | Y | MEDCIN Identifier | http://en.wikipedia.org/wiki/MEDCIN | no | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 9 | GEMS_ID | No | No | VARCHAR2(40) | Y | GEMS Identifier | no | ||||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 10 | SENSITIVITY_IND | Yes | Yes | CHAR(1) | Y | Sensitivity Indicator | Y = Sensitive, N = Non-Sensitive | no | |||||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 11 | ICD93 | No | No | VARCHAR2(4) | Y | ICD93 Code | This value may not be of interest to ArmySTARRS. TMDS recommendation is to work with the ICD9_CODE value only. | There isn't an ICD95 element in the PEM_ICD9_HIST table? | This value may not be of interest to ArmySTARRS. TMDS recommendation is to work with the ICD9_CODE value only | no | |||||||||||
| TMDS | 9 | PEM_ICD9_HIST | 12 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 10 | PEM_INPATIENT | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 10 | PEM_INPATIENT | 2 | PEOPLE_ID | Yes | Yes | NUMBER | Y | People Identifier | no | ||||||||||||||
| TMDS | 10 | PEM_INPATIENT | 3 | PEM_INPATIENT_ID | Yes | Yes | NUMBER | N | PK | Inpatient Identifier | These are PK and FK values for referential integrity and they will be provided as part of the extract, but they are of no value wrt to medical analysis of data. | We need this ID in addition to PEM_ID? | These are PK and FK values for referential integrity and they will be provided as part of the extract, but they are of no value wrt to medical analysis of data. | no | ||||||||||
| TMDS | 10 | PEM_INPATIENT | 4 | MTFID | Yes | Yes | VARCHAR2(80) | Y | Military Treatment Facility Identifier | yes | yes | |||||||||||||
| TMDS | 10 | PEM_INPATIENT | 5 | ADMIT_DATE | Yes | Yes | DATE | Y | Identification Number for the Medication | The "title" and FieldName don’t match at all. What is the relationship of this table to PEM - Can there be multiple PEM_INPATIENT records for one PEM, or just one? Is this an inpatient episode (admit to discharge)? What does "medication" in the title have to do with it? | There can be multiple PEM_INPATIENT details to one PEM. | no | ||||||||||||
| TMDS | 10 | PEM_INPATIENT | 6 | ADMISSION_TYPE | Yes | Yes | VARCHAR2(100) | Y | Type Of Admission | Free Text | Is this categorized at all, or just free text? I'm used to seeing a picklist that has "elective", "urgent", and a few other categories. | Free Text | no | |||||||||||
| TMDS | 10 | PEM_INPATIENT | 7 | DISCHARGE_DATE | Yes | Yes | DATE | Y | Discharge Date | Assuming one record = one episode, with an admit date and discharge date. | Multiple PEM_INPATIENT entries are tied to one PEM. The Inpatient event has an Admission and Discharde ( two PEM_INPATIENT entries) as well as other events which have their own row in PEM_INPATIENT details table. | no | ||||||||||||
| TMDS | 10 | PEM_INPATIENT | 8 | DISCHARGE_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Discharge Comments | no | |||||||||||||
| TMDS | 10 | PEM_INPATIENT | 9 | POST_DISCHARGE_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Post Discharge Comments | Unsure of whether they are follow-up visit comments. The name of the field from a data source is labelled as "Post Discharge Comments", not sure what is the value. | Are these follow-up visit comments? | We don't know. The name of the field from a data source is labelled as "Post Discharge Comments", not sure what is the value.. [NO ANSWER] | no | ||||||||||
| TMDS | 10 | PEM_INPATIENT | 10 | ADMIT_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Admit Comments | no | |||||||||||||
| TMDS | 10 | PEM_INPATIENT | 11 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 10 | PEM_INPATIENT | 12 | SRC_INPATIENT_ID | No | No | NUMBER | Y | SRC Inpatient Identifier | What is the SRC? | SRC means “source”, i.e. data source. These are internal values from the AHLTA-T files sent to TMDS. Our recommendation is to omit these values from the feed. | no | ||||||||||||
| TMDS | 10 | PEM_INPATIENT | 13 | SRC_OUTPATIENT_ID | No | No | NUMBER | Y | SRC Outpatient Identifier | What is the SRC? | SRC means “source”, i.e. data source. These are internal values from the AHLTA-T files sent to TMDS. Our recommendation is to omit these values from the feed. | no | ||||||||||||
| TMDS | 10 | PEM_INPATIENT | 14 | OUTPATIENT_ID | Yes | Yes | NUMBER | Y | Outpatient Identifier | Y = OUTPATIENT ENCOUNTER N = INPATIENT ENCOUNTER |
This indentified that the specific medical encounter is an Outpatient encounter ( if OUTPATIENT_ID = Y) and Inpatient encounter if ( OUTPATIENT_ID = N). If a patient is admitted from outpatient setting the record is considered Inpatient and OUTPATIENT_ID = N. | 1. Does this mean they were admitted from outpatient setting, which is quite common, or that an outpatient came to an inpatient facility for some special consultation/test? 2. What is this? What does the number mean? Is this an FK to another table? | 1. This indentified that the specific medical encounter is an Outpatient encounter ( if OUTPATIENT_ID = Y) and Inpatient encounter if ( OUTPATIENT_ID = N). If a patient is admitted from outpatient setting the record is considered Inpatient and OUTPATIENT_ID = N 2. [NO ANSWER] | no | ||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 2 | PEM_INPATIENT_ID | Yes | Yes | NUMBER | N | FK to PEM_INPATIENT | Inpatient Identifier | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 3 | PEM_INPATIENT_DETAIL_ID | Yes | Yes | NUMBER | N | PEM Inpatient Detail Identifier | no | I think this is a foreign key? | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 4 | NOTE_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Detailed Note Comments | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 5 | SERVICE_TYPE | No | Yes | VARCHAR2(50) | Y | Hospital Service Type | Free Text | Is this categorized? | This is free text field and is not categorized. | no | |||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 6 | HOSPITAL_DAYS | Yes | Yes | NUMBER | Y | Hospital Days | What is the definition of "Hospital Days"? If this is one-to-many with Inpatient, what count of days are they using? | Data is provided by AHLTA-T, we need AHLTA-T developer to clarify the meaning of this value. | AHLTA-T | no | |||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 7 | APPOINTMENT_STATUS | No | No | VARCHAR2(100) | Y | Appointment Status | Is this categorized? What sort of "appointment" is going on here in this "inpatient detail"? | Data is provided by AHLTA-T, we need AHLTA-T developer to clarify the meaning of this value. | AHLTA-T | no | |||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 8 | REPORT_DATE | Yes | Yes | DATE | Y | Report Date | Is this the date the record was added? | date when the actual message was created. | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 9 | REPORT_TYPE | Yes | Yes | VARCHAR2(64) | Y | Report Type | Free Text; However, sample values include Admission, Transfer, Update, Treatment Note, Progress Note, Post-Op Note. | There is no look up table for this value, however it contains the title of the varous clinical notes associated with the Inpatient Care. Some sample values are: Admission, Transfer, Update, Treatment Note, Progress Note, Post-Op Note. NOTE: This is a free text field and providers can send various report/note titles. |
What kind of reports? Meta data vs. clinical relevance? Lookup table? | There is no look up table for this value, however it contains the title of the various clinical notes associated with the Inpatient Care. Some sample values are: Admission, Transfer, Update, Treatment Note, Progress Note, Post-Op Note. NOTE: This is a free text field and providers can send various report/note titles. |
no | ||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 10 | FILE_NAME | No | No | VARCHAR2(100) | Y | File Name | Is this a system field (e.g., original file TMDS got from data provider) that we don't need? | This is the actual message file name. | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 11 | ADMITTING_PROVIDER_ID | No | No | NUMBER | Y | Admitting Staff | See PEM_PROVIDER.PROVIDER_ID | yes | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 12 | ATTENDING_PROVIDER_ID | No | No | NUMBER | Y | Attending provider identifier | See PEM_PROVIDER.PROVIDER_ID | yes | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 13 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 14 | SRC_UNIQUE_ID | No | No | VARCHAR2(120) | Y | SRC Unique Identifier | no | ||||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 15 | SRC_ENCOUNTER_ID | No | No | NUMBER | Y | Source Encounter Identifier | no | ||||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 16 | DNBI_ID | No | No | NUMBER | Y | DNBI identifier | no | ||||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 17 | DISPOSITION_ID | Yes | Yes | NUMBER | Y | Disposition Identifier | yes | yes | Not too sure… shows up a few times so it may be a foreign key? | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 18 | SRC_DISPOSITION_ID | No | No | NUMBER | Y | SRC Disposition Identifier | no | ||||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 19 | SUBJECTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Subjective description | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 20 | OBJECTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Objective description | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 21 | ASSESSMENT | Yes | Yes | No | VARCHAR2(4000) | Y | Medical assessment | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 22 | PLAN_OF_CARE | Yes | Yes | No | VARCHAR2(4000) | Y | Treatment plan | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 23 | PREVENTIVE | Yes | Yes | No | VARCHAR2(4000) | Y | Preventive | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 24 | ENCOUNTER_TYPE | Yes | Yes | VARCHAR2(50) | Y | Encounter type | Is this categorized? | No | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 25 | LOSS_DAYS | Yes | Yes | NUMBER | Y | Loss Days | How is this calculated? | We do not know, we get the value and store it. | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 26 | INJURY_TYPE | Yes | Yes | NUMBER | Y | Type of injury that occurred to patient | Assuming PVLIST, attribute=Injury_type. How is this algorithm run? What about for multiple inpatient_detail records for one inpatient episode? | each row in pem_inpatient details is part of the entire Inpatient stay. | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 27 | TOBACCO_USE | Yes | Yes | No | VARCHAR2(4000) | Y | Tobacco use narrative | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 28 | ALCOHOL_USE | Yes | Yes | No | VARCHAR2(4000) | Y | Alcohol use narrative | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 29 | CHIEF_COMPLAINT | Yes | Yes | No | VARCHAR2(4000) | Y | Main Complaint from the patient | no | |||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 30 | HEIGHT | No | Yes | VARCHAR2(32) | Y | Patient's Height | How is this coded? Are units assumed? | inches | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 31 | WEIGHT | No | Yes | VARCHAR2(32) | Y | Patient's Weight | How is this coded? Are units assumed? | each row in pem_inpatient details is part of the entire Inpatient stay. | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 32 | PEM_TIMESTAMP | No | No | DATE | Y | PEM Timestamp | Do we need this to decode most recent record? | no, this is when record was inserted in DB | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 33 | SENSITIVITY_LEVEL | Yes | Yes | NUMBER | Y | Sensitivity Level | 1 = Sensitive, 0 = Non-Sensitive | What do the different numbers mean in terms of sensitivity level? What is meant by sensitivity? | 0- not sensitive, 1 -sensitive | no | |||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 34 | MAPPED_DNBI_CATEGORY | No | No | VARCHAR2(40) | Y | DNBI Category Mapped To This PEM | What are these categories? | TMDS ICD9 to DNBI Mapping | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 35 | SIGNED_DATE | No | No | DATE | Y | Signed Date | What does this date signify? | when provider signed the encounter | no | ||||||||||||
| TMDS | 11 | PEM_INPATIENT_DETAILS | 36 | ENCOUNTER_DATE | Yes | Yes | DATE | Y | The date this encounter occurred | Assuming date the encounter the subject of the detail was made, correct? | yes | no | ||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 1 | PEM_ID | Yes | Yes | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 2 | MED_SEQ | Yes | Yes | NUMBER | N | Medication Sequence | This is a DB related value, intendet to give a sequence id to each medication associated with a specific PEM. | What is this? | This is a DB related value, intended to give a sequence id to each medication associated with a specific PEM. | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 3 | PEM_INPATIENT_DETAIL_ID | Yes | Yes | NUMBER | Y | PEM Inpatient Detail Identifier | Assuming FK to PEM_INPATIENT_DETAIL. Is this the one-to-many relationship - where PEM_MEDICATIONS is a child table to PEM_INPATIENT_DETAIL and PEM | PEM_MEDICATIONS is a child table to PEM, but is also related to PEM_INPATIENT_DETAILS | no | I think this is a foreign key? | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 4 | MEDICATION_NAME | Yes | Yes | VARCHAR2(250) | Y | Name of the Medication | Please describe how this is categorized, if at all | AHLTA-T provides us with the Medication Name | AHLTA-T | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 5 | DRUG_ID | Yes | Yes | VARCHAR2(80) | Y | Identification Number for the Medication | Per doco, TMDS does not have the picklist to decode this, but AHLTA-T does. Can we get that? | TMDS is not the AHLTA-T developer. Please coordinate with DHIMS as the owner of the AHLTA_T product. | DHIMS | yes | yes | This id is provided by external system (AHLTA-T) and are assumed to reference known Drug IDs look up tables. Still Look for it? | |||||||||
| TMDS | 12 | PEM_MEDICATIONS | 6 | DOSAGE | Yes | Yes | VARCHAR2(80) | Y | Dosage administered | How is this coded? How are units coded? | Free text. Example: T1 po q4h prn | no | can be unique… no pick list | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 7 | QUANTITY | Yes | Yes | NUMBER | Y | Quantity Of Medicine | How is this coded? | This is a number. | no | ||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 8 | OTC_IND | Yes | Yes | CHAR(1) | Y | Over The Counter Indicator | How is this coded? | This appears to be an empty field. | no | yes | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 9 | REFILLS | Yes | Yes | NUMBER | Y | Total Refills | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 10 | REFILLS_REMAINING | Yes | Yes | NUMBER | Y | Refills Remaining | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 11 | DAYS_SUPPLY | Yes | Yes | NUMBER | Y | Total Number Of Days Supply | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 12 | ORDER_DATE | Yes | Yes | DATE | Y | Date Medication Was Ordered | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 13 | ORDER_EXPIRE_DATE | Yes | Yes | DATE | Y | Date That Order Expires On | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 14 | FILL_DATE | Yes | Yes | DATE | Y | Date The Prescription Was Filled | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 15 | COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | PEM MEDICATIONS Comments | no | |||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 16 | FDB_MEDICAL_ID | No | No | NUMBER | Y | FDB Medical Identifier | We are unsure if this value is Food and Drug Board. We are unsure if the identifier is akin to a provider's DEA number. We get this value from AHLTA-T system. AHLTA-T engineers/ DHIMS SMEs should be able to clarify what is the meaning of the value. | Is Food & Drug Board? Is the identifier akin to a provider's DEA number? | We do not know. We get this value from AHLTA-T system. AHLTA-T engineers/ DHIMS SMEs should be able to clarify what is the meaning of the value. Here is an example from our Training Tier:273529 ( Not sure what this mapps to) |
AHLTA-T | yes | yes | This id is provided by external system (AHLTA-T) and are assumed to reference known Drug IDs look up tables. Still Look for it? | ||||||||
| TMDS | 12 | PEM_MEDICATIONS | 17 | OVERRIDE_REASON | Yes | Yes | NUMBER | Y | Reason For Override | Is there a way to decode number? | We do not have the look up values. | yes | yes | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 18 | OVERRIDE_COMMENT | Yes | Yes | VARCHAR2(255) | Y | Override Comment | Free Text | May have PII, right? | We don't know, every free text may contain PII | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 19 | START_DATE | Yes | Yes | DATE | Y | Date medication was started | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 20 | STOP_DATE | Yes | Yes | DATE | Y | Date the medication will be stopped | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 21 | GEMS_ID | No | No | VARCHAR2(40) | Y | GEMS Identifier | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 22 | WARNINGS | No | No | VARCHAR2(255) | Y | Drug Warnings | Are these standard verbiage? | Duplicate Drug Warnings, Not sure if the verbiage is standard. | no | ||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 23 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 24 | AHLTAT_DATAID | Yes | Yes | NUMBER(20) | Y | Data ID | Dataid is the data identification number. | Internal TMDS DB value obtained from AHLTA-T/M files. | Is this element essential for linking requested data elements? | We use this value as part of the TMDS UI logic to display unique list of medications for a patient. TMDS recommendation is to keep this value in the extract because it will help with identifying duplicate medication entries. ( NOTE: AHLTA-T files send the same medication in multiple files, consequently it is stored multiple times in TMDS and logic needs to be employed to derive a distinct medication list.) | no | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 25 | AHLTAT_UNIT_NUMBER | Yes | Yes | NUMBER(10) | Y | Unit Number | Unit_number is the primary key for all the patients. A unique integer assigned to a member at the time the member's dataset was created. It is local cache generated unit number. | This value is populated by AHLTA-T files only and represnts the unique DB Id for a patient at a AHLTA-T facility. | All the AHLTAT elements come from the provider note in AHLTAT? The corresponding elements above are from TC2? | This value is populated by AHLTA-T files only and represnts the unique DB Id for a patient at a AHLTA-T facility. | no | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 26 | AHLTAT_SIG | Yes | Yes | VARCHAR2(120) | Y | SIG | SIG is SIG. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] (TMDS) - We are not sure what is unclear for this item and is treated as "NO ANSWER" |
no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 27 | AHLTAT_ORDERNUMBER | Yes | Yes | VARCHAR2(50) | Y | Order Number | Ordernumber is the order number. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 28 | AHLTAT_STATUSNCID | Yes | Yes | NUMBER | Y | Status Numerical Concept ID | Statusncid is the status numerical concept identification number. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | yes | yes | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 29 | AHLTAT_NATIONALDRUGCODE | Yes | Yes | VARCHAR2(20) | Y | National Drug Code | Nationaldrugcode is the national drug code. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | yes | yes | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 30 | AHLTAT_UPDATEFLAG | Yes | Yes | VARCHAR2(1) | Y | Update Flag | Updateflag is the flag to indicate if update. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | yes | yes | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 31 | AHLTAT_CREATEDON | Yes | Yes | DATE | Y | Created On | Createdon is the created date. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 32 | AHLTAT_UPDATEDON | Yes | Yes | DATE | Y | Updated On | Updatedon is the date who updated. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | no | |||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 33 | AHLTAT_TMIP_STATUS | Yes | Yes | NUMBER | Y | TMIP Status | The tmip_status is for data manager transfer from LDDB to TMIP. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | yes | yes | ||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 34 | AHLTAT_ENC_NUM | Yes | Yes | VARCHAR2(16) | Y | ENC Number | The enc_num is to store encounter number. | 1. For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. 2. All the AHLTAT elements come from the provider notes in AHLTAT? The corresponding elements above are from TC2? | 1. The PEM_MEDICATIONS table is populated with data derived from the AHLTA_T system. the PEOPLE_MSG_MEDS table is populated with medicaitons from TC2. 2. I am not sure what is meant by " The corresponding elements above are from TC2?" [NO ANSWER] | yes | yes | not too sure? | |||||||||
| TMDS | 12 | PEM_MEDICATIONS | 35 | AHLTAT_EXPANDED_SIG | Yes | Yes | No | VARCHAR2(1024) | Y | Expanded SIG. | no | |||||||||||||
| TMDS | 12 | PEM_MEDICATIONS | 36 | AHLTAT_DOSAGE_FORM | Yes | Yes | VARCHAR2(60) | Y | Dosage form. | For the fields starting in AHLTAT - please describe which ones contain unique data that we would want, and not system data that helps TMDS only. | each row is assumed to contain unqiue data. We are not sure how can we determine what elements you may need. None of these elements are internal to TMDS DB | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 1 | PEM_ID | No | No | NUMBER | N | FK to PEM | Patient Encounter Identifier | PEM_ORDERS is seldomly used and populated. | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 2 | ORDER_ID | No | No | NUMBER | N | Order Identifier | Is this the PK for this table? | sequence id, not PK | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 3 | PEM_INPATIENT_DETAIL_ID | No | No | NUMBER | Y | Patient Encounter Detail Identifier | Assume FK to PEM_INPATIENT_DETAILS. Is this a child table of that table? Meaning that these are only inpatient orders? | A specific oder associated with a PEM INPATIENT DETAIL | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 4 | ORDER_TYPE | No | No | VARCHAR2(50) | Y | Order Type | Is this categorized? | no | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 5 | ORDER_TYPE_DESC | No | No | VARCHAR2(256) | Y | Order Type Description | Is this a standard descriptor (e.g., whenever ORDER_TYPE = A, this descriptor = AFSLDKJF)? | no | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 6 | COMMENTS | Yes | No | No | VARCHAR2(4000) | Y | Order Comments | no | |||||||||||||
| TMDS | 13 | PEM_ORDERS | 7 | ORDER_DATE | No | No | DATE | Y | Date Of Order | no | ||||||||||||||
| TMDS | 13 | PEM_ORDERS | 8 | STATUS | No | No | VARCHAR2(32) | Y | Order Status | Is this categorized? | no | no | ||||||||||||
| TMDS | 13 | PEM_ORDERS | 9 | ANCILLARY_COMMENT | Yes | No | No | VARCHAR2(4000) | Y | Ancillary Order Comments | no | |||||||||||||
| TMDS | 13 | PEM_ORDERS | 10 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 1 | PEM_ID | No | No | NUMBER | N | FK to PEM | Patient Encounter Module Identifier | no | |||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 2 | PEM_INPATIENT_DETAIL_ID | No | No | NUMBER | Y | Pem Inpatient Detail Identifier | Assume FK to PEM_INPATIENT_DETAILS. Is this a child table of that table? Meaning that these are only inpatient procedures? | yes | no | ||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 3 | PROCEDURE_ID | No | No | NUMBER | N | Procedure Identifier | This is an internal TMDS DB sequence value and is not a standard CPT or MEDCIN Id code that can be mapped to a procedure. Here are some examples of MEDCID_IDS and PROCEDURE DESCRIPTION 19270, 24-Hour Ambulatory Blood Pressure Monitoring 42953, Anesthesia For Oral Cavity Procedures Please let us know if the new sample extract should contain any PEM_PROCEDURE elements. |
Can we get some examples of procedures? It is unclear if elements found in the PEM_PROCEDURES table would provide us with useful information about the pt's health/mental health condition or treatment? | This is an internal TMDS DB sequence value and is not a standard CPT or MEDCIN Id code that can be mapped to a procedure. Here are some examples of MEDCID_IDS and PROCEDURE DESCRIPTION 19270, 24-Hour Ambulatory Blood Pressure Monitoring 42953, Anesthesia For Oral Cavity Procedures Please let us know if the new sample extract should contain any PEM_PROCEDURE elements. |
no | |||||||||||
| TMDS | 14 | PEM_PROCEDURES | 4 | PROCEDURE_DESCRIPTION | Yes | No | No | VARCHAR2(4000) | Y | Procedure Description | Isn't this a standardized canned descriptor? | should be | no | |||||||||||
| TMDS | 14 | PEM_PROCEDURES | 5 | PROBLEM_HISTORY | No | No | VARCHAR2(50) | Y | Problem History | Is this free text? If not, how is it coded? | free text | no | ||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 6 | MEDCIN_ID | No | No | NUMBER | Y | Medicine Identifier | Assume FK to MEDCIN table. What is MEDCIN system? | answered above | no | ||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 7 | NOTED_DATE | No | No | DATE | Y | Noted Date | Is this the date that the record was created (even if the procedure itself occurred on a different date)? | Not sure what this date means, need to get clarificaiton from AHLTA-T developer. | AHLTA-T | no | |||||||||||
| TMDS | 14 | PEM_PROCEDURES | 8 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 9 | PROCEDURE_CODE | No | No | VARCHAR2(30) | Y | Procedure Code | Is this a standardized descriptor? | this field appears to be blanc. | no | ||||||||||||
| TMDS | 14 | PEM_PROCEDURES | 10 | CODING_SYSTEM | No | No | VARCHAR2(30) | Y | Coding System | Is it necessary to get this field along with PROCEDURE_CODE to decode the procedure code? Please explain. | this field appears to be blanc. | no | ||||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 1 | PEM_ID | Yes | Yes | NUMBER | N | Unit Identifier for the Medical Treatment Facility (MTF) | Assume FK to PEM table - although Title column suggests that this is something else…? | FK to PEM. | no | ||||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 2 | SYMPTOMS_ID | Yes | Yes | NUMBER | N | Identification number for the event | Per doco, this is a sequence number, not a reference value. Does this mean that symptoms can be duplicated? Is there a date associated with the report of these symptoms? I don’t see a date in this table. | These are the symptoms that came with the encounter. The date of the encounter is in the PEM.ENCOUNTER_DATE | no | its a sequence number | |||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 3 | MAJOR | Yes | Yes | VARCHAR2(250) | Y | Major Symptom noted | Free Text | Is this free text? If not, how is it coded? | free text | no | |||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 4 | MINOR | Yes | Yes | VARCHAR2(250) | Y | Minor Symptom noted | Free Text | Is this free text? If not, how is it coded? | free text | no | |||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 5 | DURATION | Yes | Yes | NUMBER | Y | Length of time the symptom has been present | Does this go with DURATION_UNIT? | yes | no | ||||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 6 | DURATION_UNIT | Yes | Yes | VARCHAR2(10) | Y | Unit of measurement | Free Text | No picklist is noted in doco, is this free text? | free text | no | |||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 7 | MEDCIN_ID | Yes | Yes | NUMBER | Y | Medicine Identifier | http://en.wikipedia.org/wiki/MEDCIN | Why would there be a pointer to MEDCIN? | becausae every symptom has a correspondign MEDCINID. | no | |||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 8 | GEMS_ID | No | No | VARCHAR2(40) | Y | GEMS Identifier | no | ||||||||||||||
| TMDS | 15 | PEM_SYMPTOMS | 9 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 1 | PEM_ID | Yes | Yes | NUMBER | N | Patient Encounter Module Identifier | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 2 | SYMPTOMS_ID | Yes | Yes | NUMBER | N | Identification number for the event | no | its a sequence number | |||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 3 | PEM_INPATIENT_DETAIL_ID | Yes | Yes | NUMBER | Y | PEM Inpatient Detail Identifier | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 4 | MAJOR | Yes | Yes | VARCHAR2(250) | Y | Major Symptom noted | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 5 | MINOR | Yes | Yes | VARCHAR2(250) | Y | Minor Symptom noted | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 6 | DURATION | Yes | Yes | NUMBER | Y | Length of time the symptom has been present | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 7 | DURATION_UNIT | Yes | Yes | VARCHAR2(10) | Y | Unit of measurement | no | values seem too obvious for a list to me | |||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 8 | MEDCIN_ID | Yes | Yes | NUMBER | Y | Medicine Identifier | http://en.wikipedia.org/wiki/MEDCIN | no | |||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 9 | GEMS_ID | No | No | VARCHAR2(40) | Y | GEMS Identifier | no | ||||||||||||||
| TMDS | 16 | PEM_SYMPTOMS_HIST | 10 | AUDIT_ID | Yes | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 17 | PMR | 1 | PMR_ID | No | No | NUMBER | N | PK | Patient Movement Record Identifier | PMR table data comes from TRAC2ES. Army STARRS has direct feed. In TMDS DB Design, the PMR table also contains JPTA registrations performed at L4 facilities such as LRMC, Walter Reed etc. Only JPTA data will be sent to ArmySTARRS, TRAC2ES data will be omitted. (Cox) Any actual encounters at Level 4 should be entered into AHLTA or CHCS, so I see no need for us to request this info. | no | ||||||||||||
| TMDS | 17 | PMR | 2 | PEOPLE_ID | No | No | NUMBER | N | FK to PEOPLE | People Identifier | no | |||||||||||||
| TMDS | 17 | PMR | 3 | PMR_IDENTIFIER | No | No | NUMBER | Y | PMR Identifier from input data source | no | ||||||||||||||
| TMDS | 17 | PMR | 4 | CITE_NUMBER | No | No | NUMBER | Y | Cite Number | What is this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 5 | PMR_STATUS | No | No | NUMBER | Y | PMR Status | We would probably only want to get the ones in certain dormant statuses (e.g., COMPLETED). What dormant statuses are there? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 6 | DB_STATUS | No | No | VARCHAR2(10) | Y | Database Status | Is this field categorized into a picklist? What does it mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 7 | AGE | No | No | NUMBER | Y | Age | no | ||||||||||||||
| TMDS | 17 | PMR | 8 | AGE_UNIT | No | No | VARCHAR2(10) | Y | Unit Of Measure For Age | no | ||||||||||||||
| TMDS | 17 | PMR | 9 | MVMT_CLASS_CODE | No | No | NUMBER | Y | Movement Class Code | How is this number decoded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 10 | REASON_REGULATED | No | No | NUMBER | Y | Regulated Reason | How is this number decoded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 11 | PRECEDENCE_ID | No | No | NUMBER | Y | Precedence Identifier | What does this mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 12 | READY_DATE | No | No | DATE | Y | Ready Date | Does this mean the date ready for transport? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 13 | COMMERCIAL_TRANSPORT | No | No | CHAR(1) | Y | Commercial Transportation | Is this a flag? What are the values? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 14 | LITTER_SPACES | No | No | NUMBER | Y | Number Of Litter Spaces | What is a litter space? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 15 | AMBULATORY_SPACES | No | No | NUMBER | Y | Number Of | What does this field mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 16 | CCATT | No | No | CHAR(1) | Y | CCATT | What does this field mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 17 | ORIGIN_FACILITY_CODE | No | No | VARCHAR2(80) | Y | Origin Facility Code | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 18 | ORIGIN_FACILITY_NAME | No | No | VARCHAR2(250) | Y | Origin Facility Name | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 19 | ORIGIN_THEATER | No | No | VARCHAR2(32) | Y | Origin Theater | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 20 | DEST_FACILITY_CODE | No | No | VARCHAR2(80) | Y | Destination Facility Code | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 21 | DEST_FACILITY_NAME | No | No | VARCHAR2(250) | Y | Destination Facility Name | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 22 | DEST_THEATER | No | No | VARCHAR2(32) | Y | Destination Theater | How is this field decoded, or is it free text? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 23 | CASUALTY_EVENT | No | No | VARCHAR2(30) | Y | Casualty Event | What does this mean? Does it relate to the DCIPS/Casualty dataset? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 24 | INJURY_TYPE | No | No | NUMBER | Y | Type of injury that occurred to patient | Is this an FK to PVLIST where attribute=injury_type? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 25 | ADMITTED_MTF | No | No | VARCHAR2(100) | Y | Admitted Treat Facility | How to decode this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 26 | ADMISSION_DATE | No | No | DATE | Y | Admission Date | Will this date match theoretically a PEM date? In other words, should there be a PEM record associated in some way to a PMR record? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 27 | LAST_KNOWN_ITV_EVENT | No | No | NUMBER | Y | Last Known ITV Event | What is an ITV event? What does the number mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 28 | LAST_LOCATION | No | No | VARCHAR2(100) | Y | Last Location | Is this free text? If not, how is it coded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 29 | LAST_LOCATION_DATE | No | No | DATE | Y | Last Location Date | What does this mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 30 | DISPOSITION_DATE | No | No | DATE | Y | Disposition Date | Is this the disposition of the related PEM record? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 31 | DISPOSITION_ID | No | No | NUMBER | Y | Disposition Identifier | Is there a picklist? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 32 | DISPOSITION_COMMENTS | Yes | No | No | VARCHAR2(4000) | Y | Disposition Comments | no | |||||||||||||
| TMDS | 17 | PMR | 33 | NUM_ATTENDANTS | No | No | NUMBER | Y | Number Of Attendants | How is "attendants" defined? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 34 | NUM_MEDICAL_ATTENDANTS | No | No | NUMBER | Y | Number Of Medical Attendants | How is "medical attendants" defined? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 35 | NUM_NON_MEDICAL_ATTENDANTS | No | No | NUMBER | Y | Number Non-Medical Attendants | How is "non-medical attendants" defined? Should the number of medical and non-medical add up to attendants total? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 36 | HAS_ITINERARY | No | No | CHAR(1) | Y | Has Itinerary | What does this mean? How is it coded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 37 | PROPOSED_ARRIVAL_DATE | No | No | DATE | Y | Proposed Arrival Date | no | ||||||||||||||
| TMDS | 17 | PMR | 38 | MISSION_ID | No | No | VARCHAR2(35) | Y | Mission Identifier | Is this categorized? Is it an FK to a picklist? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 39 | AIRCRAFT_TYPE | No | No | VARCHAR2(15) | Y | Aircraft Type | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 40 | NUM_MISSIONS | No | No | NUMBER | Y | Number Of Missions | What does this mean - number of missions the transport is serving? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 41 | NUM_RON_STOPS | No | No | NUMBER | Y | Number Of Stops | What does this mean - number of stops on the transport? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 42 | HISTORY | Yes | No | No | VARCHAR2(4000) | Y | History | no | |||||||||||||
| TMDS | 17 | PMR | 43 | CASE_ID | No | No | VARCHAR2(120) | Y | Case Identifier | Is this an FK to another table? There is a CASE_ID in the PEM table - should we be getting a CASE table to connect all this together? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 44 | ORIGINAL_DATE | No | No | DATE | Y | Original Date | What does "original date" mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 45 | DATA_SOURCE | No | No | VARCHAR2(50) | Y | PMR Data Source | Is this an internal TMDS field? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 46 | FILE_NAME | No | No | VARCHAR2(100) | Y | Data Source File Name | Is this an internal TMDS field? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 47 | ORIG_DISPOSITION_ID | No | No | NUMBER | Y | Original Disposition Identifier | Is this an internal TMDS field? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 48 | VIP_TYPE_ID | No | No | NUMBER | Y | Very Important Person Type Identifier | Please describe this variable. How is it coded? Should we use it to remove these records (e.g., records of the President or top Generals)? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 49 | PATIENT_CONDITION_ID | No | No | NUMBER | Y | Patient Condition Identifier | Does this have a picklist associated? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 50 | AMPUTATION_CAUSE_ID | No | No | NUMBER | Y | Amputation Cause Identifier | Does this have a picklist associated? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 51 | MEDICAL_SERVICE_ID | No | No | NUMBER | Y | Medical Service Identifier | Does this have a picklist associated? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 52 | OPEN_IND | No | No | CHAR(1) | Y | Open Indicator | How is this coded? What does "open" mean? If this is status of record, maybe we should only get "closed" ones? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 53 | PMR_TIMESTAMP | No | No | DATE | Y | PMR Timestamp | Do we need this to keep track of our updates? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 54 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 17 | PMR | 55 | SENSITIVE_IND | No | No | CHAR(1) | Y | Does the record contain sensitive information | Y = Sensitive, N = Non-Sensitive | What is meant by sensitive? | [NO ANSWER] | no | |||||||||||
| TMDS | 17 | PMR | 56 | WARD_BILLETING_ID | No | No | NUMBER | Y | Ward Billeting Identifier | What is this? Assume location specific for the Soldier | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 57 | ROOM_NUMBER | No | No | VARCHAR2(100) | Y | Room number in ward_billeting_id indicating patient's location | no | ||||||||||||||
| TMDS | 17 | PMR | 58 | FLIGHT_TIME | No | No | DATE | Y | Flight Time | What does this mean? Is this how long in the air? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 59 | INCIDENT_ID | No | No | NUMBER | Y | Incident Identifier | This looks like an FK to an incident table. Do we have this table? Do we need it? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 60 | AREA_OF_OPERATION_ID | No | No | NUMBER | Y | Area Of Operation Identifier | Is this a picklist to another table? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 61 | PRE_REG_IND | No | No | CHAR(1) | N | Indicates if the JPTA registration is a pre-registration or not | Y, N | no | |||||||||||||
| TMDS | 17 | PMR | 62 | REACTIVATE_USER_ID | No | No | NUMBER | Y | Reactivate User Identifier | Assume this is for TMDS only? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 63 | REACTIVATE_DATE | No | No | DATE | Y | Reactivate Date | What is being reactivated, user? If that is true, we don’t need this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 64 | INITIAL_VISIT_IND | No | No | VARCHAR2(1) | Y | Initial Visit Indicator | N = Follow Up, Y = Initial Visit | How is "initial visit" defined? | [NO ANSWER] | no | |||||||||||
| TMDS | 17 | PMR | 65 | TRANSFER_MTFID | No | No | VARCHAR2(80) | Y | Transfer MTFID of a JPTA patient | Is there a table to decode? | [NO ANSWER] | no | ||||||||||||
| TMDS | 17 | PMR | 66 | TRANSFER_DESC | No | No | VARCHAR2(255) | Y | Transfer location of a JPTA patient | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 1 | ID | No | No | NUMBER | N | Identifier | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 2 | PMR_ID | No | No | NUMBER | N | FK to PMR | Patient Movement Record Identifier | no | |||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 3 | PMR_INPATIENT_DETAIL_ID | No | No | NUMBER | Y | PMR Inpatient Detail Identifier | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 4 | AUDIT_ID | No | No | NUMBER | N | Audit Identifier | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 5 | TITLE | No | No | VARCHAR2(80) | Y | Title | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 6 | NOTE_TEXT | Yes | No | No | CLOB | N | Free text field for note text | no | |||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 7 | SRC_UNIQUE_ID | No | No | VARCHAR2(120) | Y | SRC Unique Identifier | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 8 | NOTE_TIMESTAMP | No | No | DATE | Y | Note Timestamp | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 9 | CONTENT_TYPE | No | No | VARCHAR2(100) | N | Content Type | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 10 | FACILITY_NOTE_ENTERED | No | No | VARCHAR2(80) | Y | Facility Note Entered | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 11 | UI_UPLOADED | No | No | CHAR(1) | N | UI Uploaded | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 12 | DESCRIPTION | No | No | VARCHAR2(250) | Y | Description | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 13 | FILE_NAME | No | No | VARCHAR2(200) | Y | Name of file | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 14 | CARE_STATUS_ID | No | No | NUMBER | Y | Care Status Identifier | no | ||||||||||||||
| TMDS | 18 | PMR_APPEND_NOTES | 15 | PROC_HX_STATUS | No | No | CHAR(1) | N | Procedure HX Status | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 1 | PMR_ID | No | No | NUMBER | N | FK to PMR | Patient Movement Record Identifier | no | |||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 2 | PMR_DISP_HIST_ID | No | No | NUMBER | Y | PMR Disposition History Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 3 | MTFID | No | No | VARCHAR2(80) | Y | Military Treatment Facility Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 4 | ORIGINAL_DISPOSITION_ID | No | No | NUMBER | Y | Original Disposition Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 5 | DISPOSITION_ID | No | No | NUMBER | Y | Disposition Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 6 | LOCATION | No | No | VARCHAR2(100) | Y | Unit Location | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 7 | DISP_HIST_TIMESTAMP | No | No | DATE | Y | Disposition History Timestamp | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 8 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 9 | WARD_BILLETING_ID | No | No | NUMBER | Y | Ward Billeting Identifier | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 10 | TRANSFER_MTFID | No | No | VARCHAR2(80) | Y | The MTFID the patient was transferred to | no | ||||||||||||||
| TMDS | 19 | PMR_DISP_HIST | 11 | TRANSFER_DESC | No | No | VARCHAR2(250) | Y | The description of the facility the patient was transferred to when MTFID does not exist | no | ||||||||||||||
| TMDS | 20 | PMR_ENABLING_CARE | 1 | PMR_ID | No | No | NUMBER | N | FK to PMR | Patient Movement Record Identifier | no | |||||||||||||
| TMDS | 20 | PMR_ENABLING_CARE | 2 | ENABLING_CARE_TYPE_ID | No | No | NUMBER | N | Enabling Care Type Identifier | How do the algorithms work against PMR to determine what enabling care records to enter in this table? | [NO ANSWER] | no | ||||||||||||
| TMDS | 20 | PMR_ENABLING_CARE | 3 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 1 | PMR_ID | No | No | NUMBER | N | FK to PMR | Patient Movement Record Identifier | no | |||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 2 | MTFID | No | No | VARCHAR2(80) | Y | Military Treatment Facility Identifier | no | ||||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 3 | PRIMARY_DIAGNOSIS_IND | No | No | NUMBER | Y | Primary Diagnosis Indicator | How is this coded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 4 | ICD9_CODE | No | No | VARCHAR2(32) | Y | ICD9 Code | How is this decoded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 5 | ICD9_DIAGNOSIS | No | No | VARCHAR2(500) | Y | ICD9 Diagnosis | Not Sensitive or PII. | Why is this PII? | [NO ANSWER] | no | |||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 6 | MED_SPEC_CODE | No | No | VARCHAR2(6) | Y | Medical Specification Code | What is this code? | [NO ANSWER] | no | ||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 7 | MED_SPEC_NAME | No | No | VARCHAR2(80) | Y | Medical Specification Name | no | ||||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 8 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 9 | ICD95 | No | No | VARCHAR2(7) | Y | ICD95 Code | Please define? | [NO ANSWER] | no | ||||||||||||
| TMDS | 21 | PMR_ICD9_MEDSPEC | 10 | ICD93 | No | No | VARCHAR2(4) | Y | ICD93 Code | Please define? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 1 | PEOPLE_MSG_ID | Yes | Yes | NUMBER | N | PK | People Message Identifier | Assume PK for this table. I'm also somewhat confused about the PEOPLE schema - I realize this is sourced in TC2, but what does it cover: pharmacy? What kind of encounters? Anc services? Etc. | [NO ANSWER] | no | |||||||||||
| TMDS | 22 | PEOPLE_MSG | 2 | PEOPLE_ID | Yes | Yes | NUMBER | N | FK to PEOPLE | People Identifier | Assume FK to PEOPLE table. Don't we need the people table? | [NO ANSWER] | no | |||||||||||
| TMDS | 22 | PEOPLE_MSG | 3 | CASE_ID | No | No | VARCHAR2(120) | N | Case Identifier | Assume FK to a CASE table. Don't we need a case table? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 4 | MTFID | No | No | VARCHAR2(80) | N | Military Treatment Facility Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 5 | DATA_SOURCE | No | No | VARCHAR2(80) | N | Data Source | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 6 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 7 | MSG_TYPE_ID | No | No | NUMBER | Y | Message Type Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 8 | OBS_NAME_NCID | No | No | VARCHAR2(50) | Y | OBS Name NCID | What is this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 9 | OBS_NAME | No | No | VARCHAR2(80) | Y | OBS Name | What is this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 10 | MSG_REPORT_DATE | No | No | DATE | Y | Message Report Date | What date does this indicate? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 11 | MSG_ENCOUNTER_DATE | No | No | DATE | Y | Message Encounter Date | What date does this indicate? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 12 | REQUESTING_LOCATION | No | No | VARCHAR2(350) | Y | Requesting Location | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 13 | PERFORMING_LOCATION | No | No | VARCHAR2(350) | Y | Performing Location | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 14 | ORDER_CODE | No | No | VARCHAR2(50) | Y | Order Code | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 15 | ORDER_CODE_REASON | No | No | VARCHAR2(200) | Y | Order Code Reason | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 16 | ORDER_ID | No | No | VARCHAR2(50) | Y | Order Identifier | Is this an FK to an ORDER table? Can we get this ORDER table? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 17 | ORDER_GROUP_ID | No | No | VARCHAR2(50) | Y | Order Group Identifier | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 18 | ORDER_STATUS | No | No | VARCHAR2(50) | Y | Order Status | What values can go in here? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 19 | ORDER_QTY_TIMING_DURATION | No | No | VARCHAR2(50) | Y | Order Quantity Timing Duration | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 20 | ORDER_QTY_TIMING_INTERVAL | No | No | VARCHAR2(255) | Y | Order Quantity Timing Interval | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 21 | ORDER_QTY_TIMING_CONDITION | No | No | VARCHAR2(50) | Y | Order Quantity Timing Condition | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 22 | ORDER_QTY_TIMING_START_DATE | No | No | DATE | Y | Order Quantity Timing Start Date | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 23 | ORDER_QTY_TIMING_END_DATE | No | No | DATE | Y | Order Quantity Timing End Date | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 24 | ORDER_QTY_TIMING_UNIT_QUATITY | No | No | VARCHAR2(50) | Y | Order Quantity Timing Unit Quantity | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 25 | ORDER_QTY_TIMING_PRIORITY | No | No | VARCHAR2(50) | Y | Order Quantity Timing Priority | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 26 | ORDER_DATE | No | No | DATE | Y | Date Of Order | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 27 | ORDER_ENTERED_BY | No | No | VARCHAR2(80) | Y | Order Entered By | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 28 | ORDER_VERIFIED_BY | No | No | VARCHAR2(80) | Y | Order Verified By | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 29 | ORDERING_PROVIDER | No | No | VARCHAR2(80) | Y | Ordering Provider | Is there a picklist to decode? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 30 | ORDER_MEAL_LOCATION | No | No | VARCHAR2(80) | Y | Order Meal Location | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 31 | ORDER_COMMENTS | Yes | No | No | VARCHAR2(4000) | Y | Order Comments | no | |||||||||||||
| TMDS | 22 | PEOPLE_MSG | 32 | OBS_ID | No | No | VARCHAR2(50) | Y | OBS Identifier | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 33 | OBS_REQUESTED_DATE | No | No | DATE | Y | OBS Requested Date | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 34 | OBS_COLLECTED_DATE | No | No | DATE | Y | OBS Collected Date | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 35 | OBS_ARRIVAL_DATE | No | No | DATE | Y | OBS Arrival Date | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 36 | OBS_SPECIMEN_SOURCE | No | No | VARCHAR2(80) | Y | OBS Specimen Source | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 37 | OBS_SPECIMEN_BODY_SITE | No | No | VARCHAR2(80) | Y | OBS Specimen Body Site | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 38 | OBS_QTY_TIMING_DURATION | No | No | VARCHAR2(50) | Y | OBS Quantity Timing Duration | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 39 | OBS_QTY_TIMING_INTERVAL | No | No | VARCHAR2(50) | Y | OBS Quantity Timing Interval | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 40 | OBS_QTY_TIMING_CONDITION | No | No | VARCHAR2(50) | Y | OBS Quantity Timing Condition | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 41 | OBS_QTY_TIMING_START_DATE | No | No | DATE | Y | OBS Quantity Start Date | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 42 | OBS_QTY_TIMING_END_DATE | No | No | DATE | Y | OBS Quantity End Date | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 43 | OBS_QTY_TIMING_UNIT_QUATITY | No | No | VARCHAR2(50) | Y | OBS Quantity Timing Unit Quantity | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 44 | OBS_QTY_TIMING_PRIORITY | No | No | VARCHAR2(50) | Y | OBS Quantity Timing Priority | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 45 | OBS_RESULT_STATUS | No | No | VARCHAR2(50) | Y | OBS Result Status | What is OBS? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 46 | OBS_COMMENT | Yes | No | No | VARCHAR2(4000) | Y | OBS Comment | no | |||||||||||||
| TMDS | 22 | PEOPLE_MSG | 47 | WARNING_TYPE_ID | No | No | VARCHAR2(10) | Y | Warning Type Identifier | Is there a picklist for this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 48 | WARNING_TYPE_TXT | No | No | VARCHAR2(1000) | Y | Warning Type Text | Not Sensitive or PII. | no | |||||||||||||
| TMDS | 22 | PEOPLE_MSG | 49 | WARNING_OVERRIDE_REASON | No | No | VARCHAR2(1000) | Y | Warning Override Reason | This field is intendent for the user to provide comments why they chose to override the medicaion warning text. Not Sensitive or PII. | no | |||||||||||||
| TMDS | 22 | PEOPLE_MSG | 50 | WARNING_OVERRIDE_PERSON | No | No | VARCHAR2(80) | Y | Warning Override Person | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 51 | WARNING_OVERRIDE_DATE | No | No | DATE | Y | Warning Override Date | What is a warning override? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 52 | WARNING_OVERRIDE_TXT | No | No | VARCHAR2(250) | Y | Warning Override Text | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 53 | PATIENT_WARD_NAME | No | No | VARCHAR2(80) | Y | Patient Ward Name | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 54 | PATIENT_ROOM_ID | No | No | VARCHAR2(25) | Y | Patient Note Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 55 | PATIENT_BED_ID | No | No | VARCHAR2(25) | Y | Patient Bed Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 56 | SRC_MTFID | No | No | VARCHAR2(80) | Y | SRC MTF Identifier | no | ||||||||||||||
| TMDS | 22 | PEOPLE_MSG | 57 | ACCESSION_NUMBER | No | No | VARCHAR2(60) | Y | Accession Number | What is this? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 58 | OBS_SPECIMEN_SOURCE_NCID | No | No | VARCHAR2(300) | Y | OBS Specimen Source NCID | What is OBS? What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 59 | OBS_SPECIMEN_BODY_SITE_NCID | No | No | VARCHAR2(300) | Y | OBS Specimen Body Site NCID | What is OBS? What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 60 | ORDER_ENTERED_BY_NCID | No | No | VARCHAR2(80) | Y | Order Entered By NCID | What is OBS? What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 61 | ORDER_ENTERED_BY_SRC_TABLE | No | No | VARCHAR2(80) | Y | Order Entered By Source Table | Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 62 | ORDER_VERIFIED_BY_NCID | No | No | VARCHAR2(80) | Y | Order Verified By NCID | What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 63 | ORDER_VERIFIED_BY_SRC_TABLE | No | No | VARCHAR2(80) | Y | Order Verified By Source Table | Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 64 | ORDERING_PROVIDER_NCID | No | No | VARCHAR2(80) | Y | Ordering Provider NCID | What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 22 | PEOPLE_MSG | 65 | ORDERING_PROVIDER_SRC_TABLE | No | No | VARCHAR2(80) | Y | Ordering Provider Source Table | Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 1 | PEOPLE_MSG_DETAILS_ID | No | No | NUMBER | N | PK | People Message Details Identifier | no | |||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 2 | PEOPLE_MSG_ID | No | No | NUMBER | N | FK to PEOPLE_MSG | People Message Identifier | no | |||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 3 | OBX_NAME | No | No | VARCHAR2(50) | Y | OBX Name | What is OBX? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 4 | OBX_NAME_NCID | No | No | VARCHAR2(50) | Y | OBX Name NCID | What is OBX? What is NCID? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 5 | RESULT | Yes | No | No | CLOB | Y | Result | no | |||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 6 | RESULT_UNITS | No | No | VARCHAR2(50) | Y | Result Units | What is expected in this field? Is this interpretable without RESULT? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 7 | RESULT_STATUS | No | No | VARCHAR2(50) | Y | Result Status | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 8 | COMMENTS | Yes | No | No | VARCHAR2(4000) | Y | Comments | no | |||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 9 | CERTIFIED_DATE | No | No | DATE | Y | Certified Date | What does certified mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 10 | CERTIFIED_BY | No | No | VARCHAR2(80) | Y | Certified By | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 11 | REFERENCE_RANGE | No | No | VARCHAR2(80) | Y | Reference Range | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 12 | SENSITIVE_RESULT_IND | No | No | CHAR(1) | Y | Sensitive Result Indicator | Is this coded according to another field of a similar name: "Does the record contain sensitive information. 'Y' for sensitive, 'N' for non-sensitive". What does sensitive mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 13 | ABNORMAL_FLAG | No | No | VARCHAR2(10) | Y | Abnormal Flag | What does abnormal mean - algorithm? How is this populated? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 14 | BLOOD_PRODUCT_NCID | No | No | NUMBER | Y | Blood Product NCID | What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 15 | BLOOD_PRODUCT_ALT_NCID | No | No | NUMBER | Y | Blood Product Alternate NCID | What is NCID? Is this an internal field we don't need? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 16 | BLOOD_PRODUCT | No | No | VARCHAR2(200) | Y | Blood Product | Is this free text? If not, how is it coded? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 17 | BLOOD_UNITS_COLLECTED | No | No | NUMBER | Y | Blood Units Collected | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 18 | BLOOD_UNITS_ORDERED | No | No | NUMBER | Y | Blood Units Ordered | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 19 | BLOOD_UNITS_TRANSFUSED | No | No | NUMBER | Y | Blood Units Transfused | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 20 | BLOOD_VOLUME_ORDERED | No | No | NUMBER | Y | Blood Volume Ordered | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 21 | BLOOD_TRANSFUSION_LOCATION | No | No | VARCHAR2(200) | Y | Blood Transfusion Location | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 22 | BLOOD_TRANSFUSION_REASON | Yes | No | No | VARCHAR2(1000) | Y | Blood Transfusion Reason | no | |||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 23 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 24 | BLOOD_PRODUCT_EXP_DATE | No | No | DATE | Y | Blood Product Expiration Date | no | ||||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 25 | BLOOD_PRODUCT_TYPE | No | No | VARCHAR2(80) | Y | Blood Product Type | Is this categorized? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 26 | OBX_VALUE_TYPE | No | No | VARCHAR2(2) | Y | OBX Value Type | What is OBX? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 27 | OBX_NAME_CODING_SYSTEM | No | No | VARCHAR2(60) | Y | OBX Name Coding System | What is OBX? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 28 | CERTIFIED_BY_NCID | No | No | VARCHAR2(60) | Y | Certified By NCID | What does this mean? | [NO ANSWER] | no | ||||||||||||
| TMDS | 23 | PEOPLE_MSG_DETAILS | 29 | CERTIFIED_BY_SRC_TABLE | No | No | VARCHAR2(60) | Y | Certified By Source Table | What does this mean | [NO ANSWER] | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 1 | PEOPLE_MSG_MEDS_ID | Yes | Yes | NUMBER | N | PK | People Message Medications Identifier | PEM_MEDICATIONS is populated by AHLTA-T/M data source. PEOPLE_MSG_MEDS is populated by the TC2 data source. | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 2 | PEOPLE_MSG_ID | Yes | Yes | NUMBER | N | FK to PEOPLE_MSG | People Message Identifier | no | |||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 3 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 4 | MEDICATION_NAME_NCID | Yes | Yes | VARCHAR2(10) | Y | Name of the Medication NCID | Free text? How does this relate to the other medication fields? | This is AHLTA_T internal DB value sent to TMDS. Not a free text. | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 5 | MEDICATION_NAME | Yes | Yes | VARCHAR2(100) | Y | Name of the Medication | Free text? How does this relate to the other med fields? | This is the medication name. Other fields provide more info about this medicaiton. | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 6 | MEDICATION_CODING_SYSTEM | Yes | Yes | VARCHAR2(50) | Y | Medication Coding System | Is this a picklist? How does this relate to the other medication fields? | not free text | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 7 | ALT_MEDICATION_NAME_NCID | Yes | Yes | VARCHAR2(100) | Y | Alternate Medication Name NCID | Free text? How does this relate to the other medication fields? | not free text | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 8 | ALT_MEDICATION_NAME | Yes | Yes | VARCHAR2(100) | Y | Alternate Medication Name | Free text? How does this relate to the other med fields? | not free text | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 9 | ALT_MEDICATION_CODING_SYSTEM | Yes | Yes | VARCHAR2(50) | Y | Alternate Medication Coding System | Is this a picklist? How does this relate to the other medication fields? | [NO ANSWER] | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 10 | IV_COMPONENT_IND | No | No | CHAR(1) | Y | IV Comonent Indicator | What values can go in here? | Y and N. | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 11 | IV_ADDITIVE_COMPONENT_TYPE | No | No | VARCHAR2(10) | Y | IV Additive Component Type | Categorized? | N0 | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 12 | IV_ADDITIVE_COMPONENT_AMNT | No | No | NUMBER | Y | IV Additive Component Amount | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 13 | IV_ADDITIVE_COMPONENT_UNITS | No | No | VARCHAR2(20) | Y | IV Additive Component Units | Categorized? | N | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 14 | MEDICATION_ROUTE | Yes | Yes | VARCHAR2(60) | Y | Medication Route | Categorized? | N | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 15 | REQUESTED_AMNT_MIN | Yes | Yes | NUMBER | Y | Requested Minimum Amount | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 16 | REQUESTED_AMNT_MAX | Yes | Yes | NUMBER | Y | Requested Maximum Amount | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 17 | REQUESTED_AMNT_UNITS | Yes | Yes | VARCHAR2(30) | Y | Requested Amount Units | Categorized? | N | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 18 | REQUESTED_GIVE_PER | Yes | Yes | VARCHAR2(20) | Y | Requested Give Period | What does this mean? | TBD | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 19 | DISPENSE_AMNT | Yes | Yes | NUMBER | Y | Dispensed Amount | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 20 | DISPENSE_AMNT_UNITS | Yes | Yes | VARCHAR2(30) | Y | Dispensed Amount Units | Categorized? | NO | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 21 | REFILL_AMNT | Yes | Yes | NUMBER | Y | Refill Amount | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 22 | REFILL_AMNT_REMAINING | Yes | Yes | NUMBER | Y | Refill Amount Remaining | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 23 | REFILL_NUMBER | Yes | Yes | NUMBER | Y | Refill Number | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 24 | REFILL_MOST_RECENT_DATE | Yes | Yes | DATE | Y | Refill Most Recent Date | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 25 | INSTRUCTIONS_TO_PHARMACY | No | No | VARCHAR2(200) | Y | Instructions To Pharmacy | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 26 | INSTRUCTIONS_TO_PATIENT | Yes | Yes | VARCHAR2(200) | Y | Instructions To Patient | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 27 | PAHRMACY_DELIVERY_LOCATION | No | No | VARCHAR2(200) | Y | Pharmacy Delivery Location | no | ||||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 28 | HUMAN_REVIEW_IND | No | No | CHAR(1) | Y | Human Review Indicator | What values can go in here? | Y, N | no | ||||||||||||
| TMDS | 24 | PEOPLE_MSG_MEDS | 29 | RX_MUMBER | No | No | VARCHAR2(20) | Y | RX Number | Is this number useful in grouping records? | This is the Prescrption Number, not useful for grouping. | no | ||||||||||||
| TMDS | 25 | BH | 1 | BH_ID | Yes | Yes | NUMBER | N | PK | Behavioral Health ID | This is the unique identifier of a Behavioral Health record | no | ||||||||||||
| TMDS | 25 | BH | 2 | PEOPLE_ID | Yes | Yes | NUMBER | N | FK to PEOPLE | People ID | This is the corresponding people_id for the Behavioral Health record (references msa.people.people_id) | no | ||||||||||||
| TMDS | 25 | BH | 3 | MTFID | Yes | Yes | VARCHAR2(80) | N | Military Treatment Facility Identifier | yes | yes | |||||||||||||
| TMDS | 25 | BH | 4 | USER_ID | No | No | NUMBER | N | User ID | This is the user_id for the person that created the Behavioral Health record (references msa.users.id) | no | |||||||||||||
| TMDS | 25 | BH | 5 | BH_NOTE_TYPE_ID | Yes | Yes | NUMBER | N | Behavioral Health Note Type ID | This is the type of note created for the Behavioral Health record (references msa.xref_bh_note_type.bh_note_type_id) |
1 - Sensitive 2- BH Provider View Only |
This references XREF_BH_NOTE_TYPE. There are two values only: 1 - Sensitive 2- BH Provider View Only |
Can we get examples of note types that are in this field? | Yes, this references XREF_BH_NOTE_TYPE. There are two values only: 1 - Sensitive 2- BH Provider View Only |
no | |||||||||
| TMDS | 25 | BH | 6 | NOTE | Yes | Yes | No | CLOB | N | Note | This is the body of the Behavioral Health note | no | ||||||||||||
| TMDS | 25 | BH | 7 | SENSITIVE_INDICATOR | Yes | Yes | CHAR(1) | N | Sensitive Indicator | This indicates if the Behavioral Health record is marked as sensitive | yes | yes | ||||||||||||
| TMDS | 25 | BH | 8 | AUDIT_FMS_ID | No | No | NUMBER | N | Audit FMS ID | This is the AUDIT_FMS_ID of the record (references msa.audit_fms.id) | no | |||||||||||||
| TMDS | 25 | BH | 9 | CREATE_DATE | No | Yes | DATE | N | Create Date | Date created | These are different dates: CREATE_DATE - the date provided by the user. SYS_CREATE_DATE - the date insterted in the schema |
How does this differ from the system created dates? | These are different dates. CREATE_DATE - the date provided by the user. SYS_CREATE_DATE - the date insterted in the schema |
no | ||||||||||
| TMDS | 25 | BH | 10 | SYS_CREATE_DATE | No | No | DATE | N | System Created Date | The system generated creation date of the record. | no | |||||||||||||
| TMDS | 25 | BH | 11 | SYS_UPDATE_DATE | No | No | DATE | Y | System Updated Date | The system generated update date of the record. | no | |||||||||||||
| TMDS | 25 | BH | 12 | EXPIRED_INDICATOR | No | No | CHAR(1) | N | Expired Indicator | This indicates if the Behavioral Health record is expired (partition key) | no | |||||||||||||
| TMDS | 25 | BH | 13 | EXPIRE_DATE (TMDS) |
No | No | DATE | Y | TMDS | The date that the Behavioral Health record was marked as expired in the system | This field is obsolete and is not being used. It will be removed from this table in the next TMDS DB version. | How is expiration of a record determined? | This field is obsolete and is not being used. It will be removed from this table in the next TMDS DB version. | no | ||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 1 | BH_ATTACHMENT_ID | No | No | NUMBER | N | Behavioral Health Attachment ID | This is the unique identifier of a Behavioral Health attachment record | No attachments will be provided with the feed. Our recommendation is to remove this from the feed. | no | ||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 2 | BH_ID | No | No | NUMBER | N | Behavioral Health ID | This is the corresponding bh_id for the Behavioral Health attachment record (references msa.bh.bh_id) | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 3 | ATTACHMENT | Yes | No | No | BLOB | N | Attachment | This is the Behavioral Health attachment | no | ||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 4 | FILE_NAME | No | No | VARCHAR2(200) | N | File Name | Behavioral Health attachment file name | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 5 | CONTENT_TYPE | No | No | VARCHAR2(100) | N | Content Type | Behavioral Health attachment content type | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 6 | FILE_DESCRIPTION | No | No | VARCHAR2(200) | Y | File Description | Behavioral Health attachment file description | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 7 | USER_ID | No | No | NUMBER | N | User ID | This is the user_id for the person that created the Behavioral Health attachment record (references msa.users.id) | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 8 | UPLOAD_DATE | No | No | DATE | N | Upload Date | This is the date that the Behavioral Health attachment record was uploaded | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 9 | SYS_CREATE_DATE | No | No | DATE | N | System Created Date | The system generated creation date of the record. | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 10 | SYS_UPDATE_DATE | No | No | DATE | Y | System Updated Date | The system generated update date of the record. | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 11 | EXPIRED_INDICATOR | No | No | CHAR(1) | N | Expired Indicator | This indicates if the Behavioral Health attachment record is expired (partition key) | no | |||||||||||||
| TMDS | 26 | BH_ATTACHMENTS | 12 | EXPIRE_DATE | No | No | DATE | Y | Expired Date | The date that the Behavioral Health attachment record was marked as expired in the system | no | |||||||||||||
| TMDS | 27 | TBI | 1 | TBI_ID | Yes | Yes | NUMBER | N | TBI Identifier | no | ||||||||||||||
| TMDS | 27 | TBI | 2 | PEOPLE_ID | Yes | Yes | NUMBER | N | People Identifier | no | ||||||||||||||
| TMDS | 27 | TBI | 3 | MTFID | Yes | Yes | VARCHAR2(80) | N | Military Treatment Facility Identifier | yes | yes | |||||||||||||
| TMDS | 27 | TBI | 4 | USER_ID | No | No | NUMBER | N | USERS.ID for submitting user | no | ||||||||||||||
| TMDS | 27 | TBI | 5 | SUBMIT_DATE | Yes | Yes | DATE | N | Date the form was submitted | Do we need this for troubleshooting? Otherwise, we only care about exam date. | correct | no | ||||||||||||
| TMDS | 27 | TBI | 6 | EXAM_TYPE | Yes | Yes | VARCHAR2(15) | N | Exam Type | Is this field categorized into a picklist? | n | no | ||||||||||||
| TMDS | 27 | TBI | 7 | EXAM_DATE | Yes | Yes | DATE | N | Exam Date | no | ||||||||||||||
| TMDS | 27 | TBI | 8 | REFERRAL | Yes | Yes | VARCHAR2(5) | Y | Referral | Yes, No | Please define and provide coding for this field? | Yes, NO | no | |||||||||||
| TMDS | 27 | TBI | 9 | REFERRAL_LOCATION | Yes | Yes | VARCHAR2(80) | Y | Referral Location | How is location categorized? | no | no | ||||||||||||
| TMDS | 27 | TBI | 10 | TITLE | Yes | Yes | VARCHAR2(100) | Y | Title | What does title mean? Title of the note? This could have PII, too, if that is true. | title of the actual note | no | ||||||||||||
| TMDS | 27 | TBI | 11 | NOTE | Yes | Yes | No | VARCHAR2(4000) | Y | Note | no | |||||||||||||
| TMDS | 27 | TBI | 12 | UPDATE_DATE | Yes | Yes | DATE | Y | Timestamp when the record was updated | no | ||||||||||||||
| TMDS | 28 | TBI_ANAM | 1 | TBI_ID | Yes | Yes | NUMBER | N | TBI Identifier | Assume this is an FK back to TBI_ID in TBI table. Does TBI_ANAM have a unique identifier field? We should get it. | The TBI_ANAM Is the unique field that ties to TBI. Not sure what is the question. We are providing you with all fields in this table. | no | ||||||||||||
| TMDS | 28 | TBI_ANAM | 2 | BASELINE_IND | Yes | Yes | VARCHAR2(5) | N | Baseline Indicator | Please provide coding for this field. I understand it just says of there is an ANAM baseline. | [NO ANSWER] | yes | yes | |||||||||||
| TMDS | 29 | TBI_MACE | 1 | TBI_ID | Yes | Yes | NUMBER | N | TBI Identifier | Assume this is an FK back to TBI_ID in TBI table. Does TBI_MACE have a unique identifier field? We should get it. | [NO ANSWER] | no | ||||||||||||
| TMDS | 29 | TBI_MACE | 2 | TOTAL_SCORE | Yes | Yes | NUMBER | N | Total Score | Do you have any guidance on interpretation (e.g., anything over a certain number is considered TBI)? | Please see TBI guidelines. We are storing the data given. | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 1 | NOTE_ID | Yes | Yes | NUMBER | N | PK | Unique identifier of a note for a patient | PM=Pain Management. Almost all of these elements capture very detailed information about the procedure used to try and control pain. The provider is normally an anesthesiologist. The setting is normally immediately post-severe trauma and post-surg. This would only occasionally, if ever, deal with chronic pain. This is why I only selected a small number of elements. (TMDS) The PM "Pain Management" module is not intended for chronic pain management. |
no | ||||||||||||
| TMDS | 30 | PM_NOTES | 2 | PEOPLE_ID | Yes | Yes | NUMBER | N | FK to PEOPLE | People ID | The patient this note belongs to. All notes for a patient will point to one people record | Assume FK back to PEOPLE table, needed for SSN. What is this a child table to? | All PK and FK information was provided in previous e-mails and spreadsheets. Yes, this is FK to PEOPLE. PM refers to Pain Management. |
no | ||||||||||
| TMDS | 30 | PM_NOTES | 3 | NOTE_CATEGORY_ID | Yes | Yes | NUMBER | N | Note Category ID | The general category of this note (procedure, clinical or transfer) | Is there a picklist - values are text, but field is numeric? | yes | yes | yes | ||||||||||
| TMDS | 30 | PM_NOTES | 4 | PROCEDURE_TYPE_ID | Yes | Yes | NUMBER | Y | Procedure Type ID | The procedure type of this note. Procedures have 4 types, this can be used without a medication_id to get only the procedure type | Is there a picklist? | Yes, you'll be able to get the list by looking at the values. | no | values are too obvious for a list | ||||||||||
| TMDS | 30 | PM_NOTES | 5 | MEDICATION_ID | Yes | Yes | NUMBER | Y | Medication ID | For procedures: The medication used in the procedure. Each procedure has a specific set of medications allowed | Is there a picklist? | yes | yes | yes | ||||||||||
| TMDS | 30 | PM_NOTES | 6 | COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Comments | For all note types: Any comments about the specific note. | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 7 | PLACEMENT_DATE | Yes | Yes | DATE | Y | Placement Date | For all note types: The user-entered date of when pain management procedure administered, when the action (e.g. transfer) occurred | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 8 | PRE_PROC_VAS | Yes | Yes | NUMBER(3) | Y | Pre-Procedure Verbal Analogue Score | For procedures: Pre-Procedure Verbal Analogue Score of 0-10 | Score 0 - 10 | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 9 | POST_PROC_VAS | Yes | Yes | NUMBER(3) | Y | Post-Procedure Verbal Analogue Score | For procedures: Post-Procedure Verbal Analogue Score of 0-10 | Score 0 - 10 | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 10 | DISCONTINUE_DATE | Yes | Yes | DATE | Y | Discontinue Date | For procedures: the date this procedure was discontinued (i.e. expire) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 11 | DISCONTINUE_TIME_IN_PLACE | Yes | Yes | NUMBER | Y | Discontinue Time In Place | For procedures: the number of days the active procedure was in place | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 12 | DISCONTINUE_CATH_INTACT_IND | No | No | CHAR(1) | Y | Discontinue Catheter Intact Indicator | For procedures: A YES/NO value to determine if the catheter tip was intact or not | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 13 | DISCONTINUE_COMMENTS | Yes | No | No | VARCHAR2(4000) | Y | Discontinue Comments | For procedures: any final comments when discontinuing the procedure | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 14 | CATHETER_TUNNELED_IND | No | No | CHAR(1) | Y | Catheter Tunneled Indicator | For CPNB: YES/NO value to determine if the catheter was tunneled or not | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 15 | LEVEL_SPINE | No | No | VARCHAR2(4000) | Y | Level Spine | For EPI CATH: short, free form value of where the catheter was placed on the patients spine | Free Text | This field is intendent to capture location of catheter placement. It does not contain PII. | no | |||||||||||
| TMDS | 30 | PM_NOTES | 16 | PCEA_IND | No | No | CHAR(1) | Y | Patient Controlled Epidural Bolus Indicator | For EPI CATH: YES/NO value to determine if the patient received Patient Controlled Epidural Bolus (PCEA). If Yes, then volume and lockout is required | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 17 | PCEA_VOLUME | No | No | NUMBER(10,3) | Y | Patient Controlled Epidural Bolus Volume | For EPI CATH: the amount of epidural bolus administered | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 18 | PCEA_VOLUME_UNIT | No | No | VARCHAR2(32) | Y | Patient Controlled Epidural Bolus Volume Unit | For EPI CATH: the unit administered (mL is expected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 19 | LOADING_DOSE_IND | No | No | CHAR(1) | Y | Loading Dose Indicator | For IV PCA: YES/NO value if the patient received a loading dose. If Yes, then loading_dose is required | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 20 | LOADING_DOSE | No | No | NUMBER | Y | Loading Dose | For IV PCA: the loading dose in mg the patient received | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 21 | LOADING_DOSE_UNIT | No | No | VARCHAR2(32) | Y | Loading Dose Unit | For IV PCA: the unit of the loading dose (mg is expected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 22 | BASAL_RATE_IND | No | No | CHAR(1) | Y | Basal Rate Indicator | For IV PCA: Basal Rate/Continuous Infusion YES/NO value. If Yes, then basal rate and basal date is required. | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 23 | BASAL_RATE | No | No | NUMBER(10,3) | Y | Basal Rate | For IV PCA: The rate of infusion in mL/hr | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 24 | BASAL_RATE_UNIT | No | No | VARCHAR2(32) | Y | Basal Rate Unit | For IV PCA: the unit of infusion rate (mL/hr is expected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 25 | BASAL_DATE | No | No | DATE | Y | Basal Date | For IV PCA: the date the basal infusion was started? administered? | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 26 | PCA_IND | No | No | CHAR(1) | Y | PCA Indicator | For IV PCA, CPNB: Patient Controlled Bolus, YES/NO value if the patient received a bolus. If Yes, pca dose and lockout is required | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 27 | PCA_VOLUME | No | No | NUMBER | Y | PCA Volume | For CPNB: the volume of the catheter bolus | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 28 | PCA_VOLUME_UNIT | No | No | VARCHAR2(32) | Y | PCA Volume Unit | For CPNB: the unit of the concentration (% is expcected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 29 | PCA_DOSE | No | No | NUMBER | Y | PCA Dose | For IV PCA: the dose in mg of the bolus | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 30 | PCA_DOSE_UNIT | No | No | VARCHAR2(32) | Y | PCA Dose Unit | For IV PCA: the dose unit (mg is expected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 31 | CURRENT_VAS | Yes | Yes | NUMBER | Y | Current Verbal Analogue Score | For CLINICAL and TRANSFER: Current Verbal Analogue Score 0-10 | Score 0 - 10 | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 32 | VAS | Yes | Yes | NUMBER | Y | Verbal Analogue Score | For CLINICAL and TRANSFER: Verbal Analogue Score 0-10 | Score 0 - 10 | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 33 | SATISFIED_IND | Yes | Yes | CHAR(1) | Y | Satisfied Indicator | For CLINICAL and TRANSFER: YES/NO value to determine if the patient was satisfied with the pain treatment | Yes, No | How is this information gathered? | [NO ANSWER] | no | ||||||||||
| TMDS | 30 | PM_NOTES | 34 | SATISFIED_COMMENTS | Yes | Yes | No | VARCHAR2(4000) | Y | Satisfied Comments | For CLINICAL and TRANSFER: to capture when the patient was dissatisfied with the pain treatment | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 35 | PAIN_PLAN | Yes | Yes | No | VARCHAR2(4000) | Y | Pain Plan | For CLINICAL and TRANSFER: doctors's notes for continued pain management | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 36 | BOLUS_INJECTION_IND | No | No | CHAR(1) | Y | Bolus Injection Indicator | For EPI CATH: YES/NO value to determine if the patient received a bolus injection, if Yes, a data, medication, concentration and volume is expected | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 37 | MTFID | Yes | Yes | VARCHAR2(80) | Y | Military Treatment Facility Identifier | Is there a reference table? | [NO ANSWER] | yes | yes | |||||||||||
| TMDS | 30 | PM_NOTES | 38 | DESTINATION_MTFID | Yes | Yes | VARCHAR2(80) | Y | Destination Military Treatment Facility Identifier | For TRANSFER: the facility the patient has transferred to | Is there a reference table? | [NO ANSWER] | yes | yes | ||||||||||
| TMDS | 30 | PM_NOTES | 39 | BLOCK_PURPOSE_ID | No | No | NUMBER | Y | Block Purpose ID | For EPI CATH, CPNB, SPNB: The reason for the pain management. | Can we decode this? | [NO ANSWER] | no | |||||||||||
| TMDS | 30 | PM_NOTES | 40 | BLOCK_LOCATION_ID | No | No | NUMBER | Y | Block Location ID | For CPNB, SPNB: the location of the nerve block. | Can we decode this? | [NO ANSWER] | no | |||||||||||
| TMDS | 30 | PM_NOTES | 41 | LATERALITY | No | No | VARCHAR2(32) | Y | Laterality | For CPNB, SPNB: The laterality of the nerve block Left or Right. | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 42 | MEDICATION_CONCENTRATION | No | No | NUMBER(10,3) | Y | Medication Concentration | For procedures: the concentration of the bolus injection | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 43 | MEDICATION_CONCENTRATION_UNIT | No | No | VARCHAR2(32) | Y | Medication Concentration Unit | For procedures: the unit of the medication concentration (%, mg/mL) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 44 | MEDICATION_VOLUME | No | No | NUMBER(10,3) | Y | Medication Volume | For EPI CATH, CPNB, SPNB: The volume of the bolus injection | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 45 | MEDICATION_VOLUME_UNIT | No | No | VARCHAR2(32) | Y | Medication Volume Unit | For EPI CATH, CPNB, SPNB: the unit of the volume | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 46 | MEDICATION_INFUSION_RATE | No | No | NUMBER(10,3) | Y | Medication Infusion Rate | For EPI CATH, CPNB: The infusion rate of the pain procedure medication | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 47 | MEDICATION_INFUSION_RATE_UNIT | No | No | VARCHAR2(32) | Y | Medication Infusion Rate Unit | For EPI CATH, CPNB: The unit of the infusion rate | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 48 | LOCKOUT | No | No | NUMBER | Y | Lockout | For IV PCA, EPI CATH, CPNB: the lockout time in minutes of the Bolus | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 49 | LOCKOUT_UNIT | No | No | VARCHAR2(32) | Y | Lockout Unit | For IV PCA, EPI CATH, CPNB: the unit of the lockout (minutes is expected) | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 50 | ADDITIONAL_BLOCK_IND | No | No | CHAR(1) | Y | Additional Block Indicator | For CPNB, SPNB: YES/NO value indicating the user created an additional note record when creating this note. | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 51 | CATHETER_BOLUS_IND | No | No | CHAR(1) | Y | Catheter Bolus Indicator | For CPNB: YES/NO value to determine if a catheter bolus was administered | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 52 | BOLUS_DATE | No | No | DATE | Y | Bolus Date | For EPI CATH, CPNB: The date of the bolus injection | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 53 | TEST_DOSE_IND | No | No | CHAR(1) | Y | Test Dose Indicator | For EPI CATH, CPNB: YES/NO value which should always be YES for these procedure types. | Yes, No | no | ||||||||||||
| TMDS | 30 | PM_NOTES | 54 | STATUS | Yes | Yes | VARCHAR2(32) | N | Status | The status of the note (Active or Discontinued) the status will only be changed by the user except the SPNB which auto-expires 24 hours after the PLACEMENT_DATE | Active, Discontinued | Will this field will be useful to us? | [NO ANSWER] | no | ||||||||||
| TMDS | 30 | PM_NOTES | 55 | DISCONTINUE_NOTE_ID | No | No | NUMBER | Y | Discontinue Note ID | For CLINICAL and TRANSFER: the parent note ID where the user discontinued this procedure | Is this table self-referential? Please describe schema. | [NO ANSWER] | no | |||||||||||
| TMDS | 30 | PM_NOTES | 56 | AUDIT_ID | No | No | NUMBER | Y | Audit Identifier | no | ||||||||||||||
| TMDS | 30 | PM_NOTES | 57 | CREATE_USER_ID | No | No | NUMBER | Y | Create User ID | The user who actually created this note record | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 58 | SYS_CREATE_DATE | No | No | DATE | N | System Created Date | The system generated creation date of the record. | no | |||||||||||||
| TMDS | 30 | PM_NOTES | 59 | SYS_UPDATE_DATE | No | No | DATE | Y | System Updated Date | The system generated update date of the record. | Do we need this, or can we just get notes that are done/won't get updated? | [NO ANSWER] | no | |||||||||||
| TMDS | 31 | PEOPLE | 1 | PEOPLE_ID | Yes | Yes | NUMBER | N | PK | People Identifier | Provide linkage to Patient Demographics information. | PEOPLE table stores the specific Patient Demographics information which was submitted with the actual medical record. | no | |||||||||||
| TMDS | 31 | PEOPLE | 2 | PATIENT_ID | Yes | Yes | NUMBER | N | FK to PATIENT | Patient ID | Provide linkage to Patient Demographics information. | no | ||||||||||||
| TMDS | 32 | PATIENT | 1 | PATIENT_ID | Yes | Yes | NUMBER | N | FK to PATIENT | Patient ID | Provide linkage to Patient Demographics information. | PATIENT people represents the patient across multiple data sources. | no | |||||||||||
| TMDS | 32 | PATIENT | 2 | FIRST_NAME | Yes | Yes | No | VARCHAR2 (80 Byte) | Y | First Name | Provide linkage to Patient Demographics information. | no | ||||||||||||
| TMDS | 32 | PATIENT | 3 | LAST_NAME | Yes | Yes | No | VARCHAR2 (80 Byte) | Y | Last Name | Provide linkage to Patient Demographics information. | no | ||||||||||||
| TMDS | 32 | PATIENT | 4 | DOB | Yes | Yes | DATE | Y | Date of Birth | Provide linkage to Patient Demographics information. | no | |||||||||||||
| TMDS | 32 | PATIENT | 5 | SPONSOR_SSN | DI | Yes | Yes | VARCHAR2 (80 Byte) | Y | Sponsor SSN | Provide linkage to Patient Demographics information. | no | ||||||||||||
| TMDS | 32 | PATIENT | 6 | FMP | Yes | Yes | VARCHAR2 (80 Byte) | Y | FMP | Provide linkage to Patient Demographics information. | no | |||||||||||||
| TMDS | 33 | PEM_PROVIDER | 1 | PROVIDER_ID | Yes | Yes | NUMBER(22) | N | PK | Provider ID | no | |||||||||||||
| TMDS | 33 | PEM_PROVIDER | 2 | NCID | Yes | Yes | NUMBER(22) | Y | NCID | We are unclear about the definition of this element. We want it added to our request because it may contain useful information about the provider (training/background/specialty). | This is a DB sequence value generated in the AHLTA-T facility DB and sent to TMDS as part of the XML file generated for a specific AHLTA-T encounter. Per AHLTA-T Developer, this value is unique at the specific AHLTA-T facility installation, but is not unique across all the facilities installations. | no | ||||||||||||
| TMDS | 33 | PEM_PROVIDER | 3 | SPECIALITY | Yes | Yes | VARCHAR2(80 Byte) | Y | Speciality | We would like to know the provider’s specialty and request additional information to help decode the values provided in this field (e.g., 293 = nurse, social worker, psychiatrist?). | We’ll provide you with a XREF table to decode the provider’s specialty | yes | yes | |||||||||||
| TMDS | 33 | PEM_PROVIDER | 4 | SIGNATURE_CLASS | Yes | Yes | VARCHAR2(32 Byte) | Y | Signature Class | Again, we want to add this element because it may tell us something about provider training/experience/expertise. We would need additional information to understand this element better. | The additional information should be requested from the AHLTA-T developer/DHIMS . TMDS receives and stores the value but we are not sure of the exact meaning for this value since this value is only being stored and not displayed via TMDS UI. [NO ANSWER] As the TMDS developer we cannot provide you with more information on this field. DHIMS POC should be able to provide you with more informaiton. |
DHIMS POC | yes | yes | ||||||||||
| TMDS | 33 | PEM_PROVIDER | 5 | MTFID | Yes | Yes | VARCHAR2(80 Byte) | Y | MTFID | What is the association between the provider and this PEM_Provider table element? Is the provider affiliated with this treatment facility or does this identify where treatment was provided? | This is the id where treatment was provided. Our understanding is that Provider is affiliated with the medical facility where treatment is provided. | yes | yes | |||||||||||
| TMDS | 33 | PEM_PROVIDER | 6 | RANK_ID | Yes | Yes | NUMBER(22) | Y | Rank ID | Rank identifier for the facility provider | We are unclear about the definition of this element. We added it to our request because it may provide useful information about provider experience/authority/training. | This is the Provider’s Rank. This value is seldom provided. | no | |||||||||||
| Unanswered Question | Answered Question | New Fields Added by Army STARRS and USAPHC | New Fields selected by Army STARRS | Removed by Army STARRS - not needed unless required for linkage | Red Bold Font means a reference table or pick list is still needed for that field |
| File Type | application/vnd.ms-office |
| Author | eichenbaum |
| Last Modified By | Shelly Finke |
| File Modified | 2014-05-12 |
| File Created | 2010-08-27 |