Network independent medical form application for generating medical forms utilizing common content storage and patient emr from permitted emr databases

A method implemented by one or more processors, the method comprising:

• receiving, at a medical consent application of a client computing device, user credentials for providing a user with access to provider-specific functionality of the medical consent application,
• wherein the medical consent application provides functionality for multiple different medical providers;
• determining, based on the user credentials, a key value and a provider-specific identifier that are stored in association with the user credentials by the medical consent application or another device associated with the medical consent application;
• establishing, using the key value and the provider-specific identifier, a secure connection between the medical consent application and the separate computing device that provides access to a medical records database,
• wherein establishing the secure connection includes providing the key value and the provider-specific identifier to the separate computing device to cause the separate computing device to share a token value with the medical consent application;
• determining, by the medical consent application or another application, a format of a plurality of formats that the medical records database stores provider patient data for a patient of the user;
• generating, based on the format for the medical records database, patient resource schema data using the provider patient data,
• wherein the provider patient data is accessed during a token session between the medical consent application and the separate computing device, and
• wherein the patient resource schema data:
• is generated in a separate format from the format of the provider patient data, and includes a field with a value for an encrypted reference to the patient;
• determining, based on the provider patient data, that the patient is scheduled to undergo a medical procedure that can require consent from the patient, or an authorized representative of the patient, before the medical procedure is initiated by a provider or the user;
• accessing, by the medical consent application and based on the medical procedure, procedure schema data that is stored in the separate format,
• wherein various medical procedure schema data is accessible to the medical consent application to generate medical consent forms for multiple different medical procedures for the multiple different medical providers;
• generating, by the medical consent application and based on the procedure schema data, consent resource schema data to be generated in response to determining that the patient is scheduled to undergo the medical procedure that can require the consent,
• wherein the consent resource schema data:
• is generated in the separate format, identifies the medical procedure, and includes the encrypted reference to the patient or a different encrypted reference to the patient;
• causing, by the medical consent application, a patient consent form to be rendered at a display interface of the client computing device using the consent resource schema data,
• wherein the patient consent form includes natural language content embodied in fields of the procedure schema data and that describes the medical procedure;
• determining that the patient, or the authorized representative of the patient, signed the patient consent form using the medical consent application or a separate application,
• wherein the patient consent form is signed via direct input to the display interface of the client computing device or other client device;
• and
• generating, by the medical consent application, updated consent resource schema data in response to determining that the patient consent form was signed,
• wherein the updated consent resource schema data includes another encrypted reference to the patient and indicates the patient consent form was signed;
• converting the updated consent resource schema data into formatted consent resource data,
• wherein converting the updated consent resource schema data includes changing the separate format of the updated consent resource data to the format of the medical records database;
• and
• providing, by the medical consent application, the formatted consent resource data to the separate computing device during the token session or a subsequent token session between the client computing device and the separate computing device.