This specification does not contain future encounters. For future visit information the appointment specification should be used. Healthjump extracts all encounters and data related to the encounter. If exclusions are needed Healthjump will define the effort via custom scope of work.
|
NAME |
TYPE |
LENGTH |
REQUIRED |
NOTES |
|
hj_import_int |
INT |
|
Y |
|
|
client_id |
VARCHAR |
100 |
Y |
Healthjump’s client identifier. |
|
visit_id |
VARCHAR |
40 |
|
When available, this should be an alternate human readable encounter id (e.g. encounter number (enc_nbr)). When not available, this should be the same as the unique encounter id. |
|
patient_id |
VARCHAR |
50 |
|
|
|
encounter_type |
VARCHAR |
200 |
|
|
|
encounter_date |
VARCHAR |
8 |
|
Format: YYYYMMDD |
|
encounter_time |
VARCHAR |
6 |
|
Format: HHMMSS |
|
location |
VARCHAR |
200 |
|
|
|
comment |
VARCHAR |
1000 |
|
|
|
encounter_id |
VARCHAR |
40 |
|
Encounter ID from the source system. Related in other tables by "encounter_id" or "enc_id". |
|
rfv_icd9 |
VARCHAR |
1000 |
|
ICD-9 describing the patient’s stated reason for seeking care. |
|
clinician |
VARCHAR |
200 |
|
The name of the rendering provider |
|
rfv_icd10 |
VARCHAR |
1000 |
|
ICD-10 describing the patient’s stated reason for seeking care. |
|
rfv_loinc |
VARCHAR |
1000 |
|
LOINC describing the patient’s stated reason for seeking care. |
|
rfv_snomed |
VARCHAR |
1000 |
|
SNOMED describing the patient’s stated reason for seeking care. |
|
member_subscriber_id |
VARCHAR |
100 |
|
Identifier assigned to patient by health plan. |
|
insurance_type |
VARCHAR |
100 |
|
|
|
hj_create_timestamp |
TIMESTAMP |
|
|
For internal Healthjump use and reference. |
|
hj_modify_timestamp |
TIMESTAMP |
|
|
For internal Healthjump use and reference. |
|
status |
VARCHAR |
100 |
|
Ex. Filed, Pushed, Signed “Y” = Locked; “N” = Not Locked |
|
row_hash |
CHAR |
32 |
|
For internal Healthjump use and reference. |