Database Administrator

1. Ability to communicate with IT staff and clinical personnel from various organizations._ 

2. Knowledge of how to organize a professional meeting including CME and CEU.

3. Knowledge of clinical evaluation data organization and collection._ 

4. Ability to communicate with public and private practices in a variety of settings._

 5. Knowledge of how a primary care practice network functions._ 

6. Ability to respond to reporting requirements.

Description_ _ Responsible for the analysis, development, modification, installation, testing and maintenance of operating systems software. Possesses a strong understanding of systems programming, graphical user interfaces and control languages. 

Evaluates vendor supplied software packages and makes recommendations to IT management. Modifies and/or debugs vendor-supplied utilities and packages. 

Modifies, installs and prepares technical documentation for system software applications. Diagnoses, isolates and de-bugs software problems and performs problem resolution. Monitors systems capacity and performance, plans and executes disaster recovery procedures and provides Tier 2 technical support._ _ Responsibilities:-_ _ 1. Developing and maintaining tools for data acquisition, normalization and importing._ _ 2. Data quality assurance._ _ 3. Installation, management, reconfiguration etc. of the Oracle database including populating the new database with data from the old database and reconfiguring the tables._ _ 4. Developing Views for each research team and managing access._ _ 5. Providing database and basic statistical tools for the OQUIN team and researchers._ _ 6. Document all processes and tools used to take data from providers and ingest it into the database._

7. Developing and maintaining data validity audits._

8. Auditing the database for missing data._ 

9. Document all decisions on data format, meaning, and rules for computed columns._ _ 

10. Owner of the staging database._ _ 11. Keeping all primary data in a repository and backed up both locally and in the Disaster Recovery Center._ _ 12. Defining and documenting all data to be collected from members._ _ _ 13. Document all issues with incoming data for transmission back to the groups who provided the data._ _ 14. Incorporating new data dictionaries based on EMR changes or additions._ _ 15. Selecting and provisioning data from external suppliers (meds, codes, deaths etc)._