Document extraction will read and write documents to S3 in the format they are natively stored in. Such as pdf, word, jpeg, png, tiff, etc.
Once extracted, document metadata will be available via Patient_Documents table in Redshift and via API get call. The file path, related patient identifiers, and document information will be provided in the API response. The S3 file path is where the document can be retrieved. Extraction times are dependent on patient volume and how far back documents are extracted.
Please reach out to your sales executive for setup/backload costs.
|HJ_Import_Int||INT||Y||For internal Healthjump use and reference.|
|Client_ID||VARCHAR||100||Y||HJ assigned id|
|Patient_ID||VARCHAR||40||Y||Patient id that joins to demographic client_patient_id|
|Encounter_ID||VARCHAR||40||N||Encounter id document is tied to, maybe empty not all documents are stored on an encounter|
|Document_Type||VARCHAR||N||Grouper in EMR index such as Clinical Document, Image Result|
|Document_Description||VARCHAR||N||Description of document such as Cardiology Progress Note|
|Document_Date||VARCHAR||8||N||Date of document - Format: YYYYMMDD
|Document_Signed_By||VARCHAR||100||N||Who wrote document|
|Document_Signed_Date||VARCHAR||8||Date document was signed|
|FIle_Name||VARCHAR||1000||Y||Name of document stored in S3|
|File_Path||VARCHAR||1000||Y||Path to document in S3|
|Fetch_Document||CHAR||1||Y||Y/N for document fetch. Y indicates document is available and path_path will be documented|
|source_file_storage_type||CHAR||1||Y||How the document was stored in the source system. 1 = Physical, 0 = Text in DB|
|source_create_timestamp||TIMESTAMP||Y||Date document was first created in the source system|
|source_modify_timestamp||TIMESTAMP||Y||Date document was last modified in the source system|
|hj_create_timestamp||TIMESTAMP||Y||For internal Healthjump use and reference.|
|hj_modify_timestamp||TIMESTAMP||Y||For internal Healthjump use and reference.|
|row_hash||CHAR||32||Y||For internal Healthjump use and reference.|