Skip to content

Latest commit

 

History

History
19 lines (15 loc) · 1.03 KB

README.md

File metadata and controls

19 lines (15 loc) · 1.03 KB

dawg-to-fhir

Retrieve patient and other data from the DAWG for PainTracker patients and transform it via FUME into FHIR resources.

  1. Get the FUME community edition and install using their instructions.

  2. Edit the FUME .env file to configure FUME port number and FHIR standards to include.

  3. Edit configurable items in the config*.env_ files:

    • Log file location
    • FHIR server endpoint
    • FHIR server auth token
    • FUME endpoint (if changed in the FUME .env file)
    • Debug level (anything less than 9 is "info/warning", 9 or greater is "debug")
    • Types of resources to include/exclude

  4. Edit configurable items in the paintracker_daily_update_dawg_to_fhir_via_fume_job.ps1 file (this file starts the FUME API, runs the Python script above and then shuts down the FUME API. It's meant to be run via Windows Task Scheduler):

    • Log file location
    • Path to local FUME instance
    • Path to Python script [paintracker_daily_update_dawg_to_fhir_via_fume.py]