dwh_patient_mvt

Description

This table represents details of each record in the parent dwh_patient_stay table, especially movements between units in a hospital during a stay.

Columns

Field User Guide ETL Conventions Datatype Required Primary Key Foreign Key FK Table
mvt_num Unique identifier bigint(64) Yes Yes No
patient_num bigint(64) Yes No Yes dwh_patient
stay_num Use this field to link the movement record to its visit. bigint(64) Yes No Yes dwh_patient_stay
entry_date Admission date timestamptz Yes No No
out_date Discharge date timestamptz No No No
mvt_entry_mode Indicates where a person was admitted from Values are not standardized yet.
Example values : Transfert, Domicile, Mutation
varchar(500) No No No
mvt_exit_mode Indicates where a person was discharged to Values are not standardized yet.
Example values : Transfert, Domicile, Mutation, Décès
varchar(500) No No No
type_mvt Represents the kind of visit that took place (inpatient, outpatient, emergency, etc.) C : Consultation
J : HDJ
U : Urgence
H : Hospitalisation
A : Ambulatoire
S : Séance
AM : Ambulatoire MCO
AP : Ambulatoire PSY
E : Externes
varchar(30) No No No
mvt_order Indicates the sequential order of patient movements within a visit. This derived field assigns a numeric ranking to each movement event based on ascending mvt_entry_date, allowing reconstruction of the temporal flow of movements during a single visit (e.g., for visualization or analysis). integer(32) No No No
department_num Service of admission bigint(64) No No Yes dwh_thesaurus_department
unit_num Unit of admission bigint(64) No No Yes dwh_thesaurus_unit
instance_mvt_id Code of the healthcare center, see hospital_instance for more informations varchar(40) No No No
mvt_origin_code Indicate source software for this movement varchar(300) No No No
id_mvt_source Unique identifier in source software varchar(300) No No No
mvt_pid Optional pseudo-identifier for a movement. Mainly included for structural consistency; not required for standard analytical use. Generated as a hash of id_mvt_source combined with mvt_salt. varchar(300) No No No
mvt_salt Optional random salt used in the hash algorithm to generate mvt_pid. varchar(300) No No No
upload_id Identifier of the pipeline integration run, used to differentiate each batch of integrated data. Defined at the start of the pipeline as datetime.now().strftime("%Y%m%d%H%M%S").
For example a batch integrated on 15/09/2025 at 00:00:00 has upload_id = 20250915000000.
bigint(64) No No No
update_date Date and time of the record’s last update. timestamptz No No No