• English

    Google Translate Disclaimer

    The Maryland Department of Information Technology (“DoIT”) offers translations of the content through Google Translate. Because Google Translate is an external website, DoIT does not control the quality or accuracy of translated content. All DoIT content is filtered through Google Translate which may result in unexpected and unpredictable degradation of portions of text, images and the general appearance on translated pages. Google Translate may maintain unique privacy and use policies. These policies are not controlled by DoIT and are not associated with DoIT’s privacy and use policies. After selecting a translation option, users will be notified that they are leaving DoIT’s website. Users should consult the original English content on DoIT’s website if there are any questions about the translated content.

    DoIT uses Google Translate to provide language translations of its content. Google Translate is a free, automated service that relies on data and technology to provide its translations. The Google Translate feature is provided for informational purposes only. Translations cannot be guaranteed as exact or without the inclusion of incorrect or inappropriate language. Google Translate is a third-party service and site users will be leaving DoIT to utilize translated content. As such, DoIT does not guarantee and does not accept responsibility for, the accuracy, reliability, or performance of this service nor the limitations provided by this service, such as the inability to translate specific files like PDFs and graphics (e.g. .jpgs, .gifs, etc.).

    DoIT provides Google Translate as an online tool for its users, but DoIT does not directly endorse the website or imply that it is the only solution available to users. All site visitors may choose to use alternate tools for their translation needs. Any individuals or parties that use DoIT content in translated form, whether by Google Translate or by any other translation services, do so at their own risk. DoIT is not liable for any loss or damages arising out of, or issues related to, the use of or reliance on translated content. DoIT assumes no liability for any site visitor’s activities in connection with use of the Google Translate functionality or content.

    The Google Translate service is a means by which DoIT offers translations of content and is meant solely for the convenience of non-English speaking users of the website. The translated content is provided directly and dynamically by Google; DoIT has no direct control over the translated content as it appears using this tool. Therefore, in all contexts, the English content, as directly provided by DoIT is to be held authoritative.

    Requesting Maryland Medical Assistance Data - Frequently-Asked Questions

    Step 1: Beginning your Data Request

    Who do I contact at Maryland Medicaid for assistance with Data Requests?
    John Parrish, Regulatory Economist III, is the point person at MDH for starting the Data Request process. Mr. Parrish can be contacted via email at mdh.medcaiddatarequests@maryland.gov  or via phone at (410) 767-5808. We encourage the principal investigator or study coordinator to schedule a teleconference with Mr. Parrish early in the process, as an opportunity for her/him to pose questions, comments and concerns (e.g., tight timelines for deliverables) at the very front end of the process. During such a teleconference, Mr. Parrish will provide an overview of Medicaid’s processes and procedures.

    Pooja Regmi, Lead Analyst, is the point person for any and all Data Use Agreement (DUA) concerns after the beginning of the generation of the DUA. Ms. Regmi can be contacted via email at pooja.regmi@maryland.gov or via phone at (410) 767-5943.
    What happens after I submit a Maryland Medicaid data request form to the Maryland Medicaid Planning Administration team? 
    The form is reviewed for completeness and clarity. A teleconference is scheduled, during which the purpose, scope and specifications of the proposed data pull are discussed and further defined. Once the specifications are refined, the request is forwarded to the team at the Hilltop Institute at UMBC responsible for providing the requested data. This team independently reviews the specified data request for feasibility and cost as well as clarity, and schedules a teleconference with the principal investigator to discuss perspectives and recommendations for optimization of the pending data pull.
    What happens after the parameters of the data request and relevant data mining criteria, such as diagnostic codes, revenue codes, etc., are fully defined?
    A statement (i.e., narrative description) of the agreed upon parameters, referred to as the Scope of Work statement, is drafted and reviewed by all involved parties. Relevant data mining criteria (such as codes and other identifiers) are appended to this statement. Upon request, the Hilltop team can provide a sample statement of the Scope of Work to serve as guidance when the research team takes next steps to draft such a narrative. To the extent necessary, the Hilltop team provides technical assistance to the research team during the drafting of this statement. After undergoing a rigorous review, this statement is finalized.
    Is there a cost associated with the fulfillment of my data request?
    Yes. This cost is estimated based upon the finalized statement of the Scope of Work. 
    What must I submit along with my data request?
    As soon as feasible, the principal investigator submits the following to the Maryland Medicaid Planning administration team (John Parrish, Regulatory Economist III is the point person at MDH for starting the Data Request process. Mr. Parrish can be contacted via email at mdh.medicaiddatarequests@maryland.gov. or via phone at (410) 767-5808):  (1) finalized statement of the scope of work; (2) that information needed from the principal investigator to customize templates for the Inter-Agency Agreement (IA) and the Data Use Agreement (DUA); and (3) a drafted MDH IRB application. MDH IRB Form 2124, available here.