TW201346824A - Systems and methods for generating, managing, and sharing digital scripts - Google Patents

Abstract

The present disclosure generally relates to improved systems and methods for generating, managing, and sharing digital scripts which are accessible to patients and/or health care providers and may be accepted by any appropriate prescription dispensary as well as a comprehensive, real-time source of patient prescription history in compliance with and furtherance of the Meaningful Use regulations. The systems and methods may support the multi-directional flow of script information to improve disease monitoring and treatment, to mitigate patient health risks like undesirable drug interactions, to identify social factors like patient ability to afford prescriptions, and to prevent prescription fraud like forged refills.

Description

System and method for generating, managing and sharing digital scripts [Reciprocal Reference of Related Applications]

The present application claims priority to U.S. Provisional Application No. 61/605,500, filed March 1, 2012, and U.S. Provisional Application No. 61/693,072, filed on August 24, 2012.

The present disclosure is directed to a system and method for performing and recording medical instructions and related treatments. More specifically, the present disclosure relates to a system and method for generating, managing, and sharing detailed and immediate resources in a digital script and/or patient prescription history.

The Health Information Technology for Economic and Clinical Health (HITECH) Act, collectively referred to as "Meaningful Use", is designed to motivate medical providers ("providers") to take patient records from paper format. Turned into an electronic format. Such methods and systems for storing and inputting electronic patient records have been studied and applied by the industry. In addition, electronic health The Electronic Health Record (EHR) and Electronic Medical Record (EMR) companies have also designed services for providers to open prescriptions via the Computerized Physician Order Entry (CPOE) software program. The medical provider applies the above services and enters the necessary information into the interface of the CPOE software program to establish a CPOE prescription. The CPOE prescription differs from the traditional paper prescription in that the CPOE prescription has not been provided to the patient, but instead is transmitted to the designated pharmacy. The patient must go to the designated pharmacy to get his/her prescription. Moreover, the CPOE prescription is delivered to the pharmacy via fax rather than being maintained in electronic format, that is, the CPOE prescription is only another version of the paper prescription.

Although the use of CPOE's electronic delivery system has alleviated the associated human error that may result from the delivery of paper prescriptions between providers and patients (eg, sloppy, incomplete or misplaced paper prescriptions), there are still A number of shortcomings can be attributed to, for example, the use of different EHR and EMR systems by different providers, and the process of going to the pharmacy due to prescription information is only one-way. In the case of CPOE prescriptions, faxed back to the paper format, issues such as image quality and potential human error (such as involving the entry of information into the pharmacy-specific system for tracking prescriptions) will resurface.

Since the CPOE prescription is bypassed from the patient and delivered directly from the provider to the pharmacy, the CPOE prescription is transmitted by multiple providers (and maintain their respective medical records), especially affecting the patient's prior review. The prescriptions are stipulated in the designated pharmacy, and the rights to complete the prescription history are compiled. In addition, even if another pharmacy is relatively convenient (for example, when the patient is on the road), give the patient The pharmacy selection is still based on the initial pharmacy specified. Thus, the designated pharmacy "owns" the CPOE prescription and any associated renewals. In other words, unless the designated pharmacy transfers the prescription to a different pharmacy or the provider has a new prescription, the patient can only use the designated pharmacy and return to the designated pharmacy when renewing the prescription. .

These existing delivery systems using CPOE prescriptions also make providers lose the opportunity to provide more efficient and complete care. Since the CPOE prescription process is only unidirectional (ie, to a designated pharmacy), the above system does not help the provider to compile a complete prescription history for the patient. For example, when the prescription is complete, renewed, or transferred, the provider is not aware of it. Similarly, unless the patient or caregiver informs the provider that the prescription is from another provider and/or the prescription was previously provided by another pharmacy, the provider is unable to obtain information about the patient's health and treatment decisions. (for example, about the interaction of potentially bad or dangerous drugs).

In accordance with and promote the "meaningful application" rules, embodiments of the present invention are directed to improved systems and methods for generating, updating, and sharing digital prescriptions that are accessible to patients and/or medical providers, and Accepted for any suitable prescription pharmacy can also be used as a detailed and immediate resource for the patient's prescription history. In some particular embodiments of the invention, the system can support a multi-directional flow of prescription data for improving disease monitoring and treatment, mitigating health risks to patients such as adverse drug interactions, and identifying patients such as patients Social factors such as the affordability of prescriptions and prevention of falsehood Make prescriptions and other prescription frauds. The aforementioned benefits can be obtained from the individual patient up to the patient population. Embodiments of the invention may also provide a patient prescription history for sharing between stakeholders (eg, other providers and caregivers) involved in patient care.

The system of the present invention is directed to an electronic system for generating, managing, and sharing digital prescriptions. In a particular embodiment, the system includes a processor for processing data relating to a digital prescription, the data including dynamic data and/or static data, and a storage medium for storing information about the digital prescription; And instructions executable by the processor, the instructions, when executed, cause the processor to merge selected portions of the dynamic data and/or the static data to create a digital prescription, and apply a security procedure to the digital prescription. To establish a preservation digital prescription. In a particular embodiment, the security procedure includes encoding and/or encrypting the digital prescription.

In a particular embodiment, the system further includes an output device for outputting the secured digital prescription. The secured digital prescription can be output to a designated branded user including one or more of a patient, a provider, a pharmacist, and a caregiver. In other embodiments, the secured digital prescription can be output to a storage device. The system can further include instructions executable by the processor that, when executed, cause the processor to store the secured digital prescription in the storage medium.

In a particular embodiment, the system can further include: an interface to communicate with a network repository in a computer network; and instructions executable by the processor, the instructions being executed to cause the processor to pass The dynamic data and/or the static data is requested for the network database. In other embodiments, the system can include instructions executable by the processor that, when executed, cause the processor to pass the The security digital prescription is output to the network database.

In particular embodiments, the static data and/or dynamic data may include one or more of the following: prescription data, command set, prescription interaction data, customized medical instructions, diagnostic codes, patient data, caregiver data, providers Information, pharmacist data, rations data, data extracted from existing digital prescriptions, insurance data, payment data, new digital prescriptions, production records, existing digital prescriptions, revisions, digital prescriptions, matching records, and remaining renewals .

In a particular embodiment, the system includes an interface for communicating with a computer network, a processor for processing data regarding the digital prescription, the data including dynamic data and/or static data, and a storage medium for Storing information about the digital prescription; and instructions executable by the processor. The execution of the instructions causes the processor to receive a security digital prescription via the interface, and extract the selected portion of the dynamic data and/or the static data from the secure digital prescription. In a particular embodiment, the instructions for extracting the selected portion include instructions for decoding and/or decrypting the secured digital prescription. In a particular embodiment, the selected portion is selected by a designated branding user. In a particular embodiment, the system further includes instructions executable by the processor that, when executed, cause the processor to store the selected portion of the extracted data. The selected portion is stored in the storage medium or network database.

The present invention is also directed to a method of generating, managing, and sharing digital prescriptions in an electronic prescription system. In a particular embodiment, the method includes the steps of selecting data regarding a digital prescription, the data including dynamic data and/or static assets Combining the dynamic data and/or selected portions of the static data to generate a digital prescription; and applying a security procedure to the digital prescription to establish a security digital prescription. The security procedure includes encoding and/or encrypting the digital prescription. In a particular embodiment, the method further includes outputting the secured digital prescription to a designated branded user or storage device. The method further includes storing the secured digital prescription in the storage medium.

In a particular embodiment, the method can include requesting the dynamic data and/or the static data from the network repository via an interface to communicate with a network repository in a computer network. The method can further include outputting the secured digital prescription to the network repository via an interface for communicating with a network repository in the computer network.

In a particular embodiment, the method includes receiving a security digital prescription via an interface for communicating with a computer network, the security digital prescription including dynamic data and/or static data; and extracting the digital prescription from the digital prescription The selected portion of the dynamic data and/or the static data. In a particular embodiment, the step of extracting the selected portion includes instructions for decoding and/or decrypting the secured digital prescription. In a particular embodiment, the selected portion is selected by a designated branding user. In a particular embodiment, the method includes storing the selected portion of the extracted material in the storage medium or network repository.

One or more embodiments of the present invention are described in detail below with reference to the drawings. Other features, objects, and advantages will be apparent from the description, drawings and claims of the invention.

100‧‧‧Digital Database

101‧‧‧Provider/First Provider

102‧‧‧ patients

103‧‧‧ caregivers

104‧‧ ‧ pharmacist

105‧‧‧ Distribution Office

106‧‧‧second provider

201, 900‧‧‧ User equipment

202‧‧‧Central processor

203‧‧‧Data machine

204‧‧‧Network

205‧‧‧Storage device

206‧‧‧User interface

207‧‧‧ transceiver

208‧‧‧ interface

301, 304-309‧‧‧ steps

302, 401, 504‧‧‧ Static data

303, 403, 505‧‧‧ Dynamic information

402, 404-408‧‧‧ steps

501-503, 506-511‧‧‧ steps

601-604‧‧ steps

801‧‧‧New digital prescription笺

802-803‧‧‧Steps

804‧‧‧Modified or terminated digital prescription笺

901, 902‧‧‧Digital prescription笺

1000‧‧‧ screenshot

1 is a network diagram of a method for generating, managing, and sharing digital prescriptions, in accordance with an embodiment of the present invention.

2 is a schematic diagram of a system for generating, managing, and sharing digital prescriptions, in accordance with an embodiment of the present invention.

3 is a flow diagram of a system for generating, managing, and sharing digital prescriptions, in accordance with an embodiment of the present invention, from the perspective of a card provider.

4 is a flow diagram of a system for generating, managing, and sharing digital prescriptions, in accordance with an embodiment of the present invention, from the perspective of a licensed patient.

5 is a flow diagram of a system for generating, managing, and sharing digital prescriptions, in accordance with an embodiment of the present invention, from the perspective of a licensed pharmacist.

FIG. 6 is a flow chart of user initialization and carding according to an embodiment of the invention.

7A-7C are flow diagrams showing a digital prescription path between card users according to an embodiment of the invention.

FIG. 8 is a flow chart of modifying and/or terminating a digital prescription according to an embodiment of the invention.

9A and 9B are screenshots of a user device of a digital prescription device according to an embodiment of the invention.

FIG. 10 is a screenshot of a web interface of a digital prescription according to an embodiment of the invention.

Overview

Embodiments of the present invention include new systems and methods for generating, managing, and releasing digital prescriptions. A digital prescription is a digital form request made by a medical provider. Digital prescriptions have the same legal effect on prescriptions as compared to conventional paper prescriptions or faxes generated by CPOE. The authority to generate a digital prescription for the provider may be subject to local laws and practices, especially when the digital prescription is related to the controlled drug or device.

Embodiments of the present invention also include new systems and new methods for accessing and sharing digital prescriptions. For example, in some embodiments, a patient may review a digital prescription, share a prescription history with other providers, and/or obtain a prescription. The system only allows the patient to access a digital prescription and information related to his/her own health (i.e., a "closed access system" associated with at least the patient). However, other users (such as providers or caregivers) can access multiple digital prescriptions given to multiple patients, or even multiple providers (ie, an "open" access). system).

A prescription is an actual drug or therapy, each of which has multiple forms, and the prescription can be obtained at a suitable pharmacy according to the prescription. The prescription may include instructions to be given to the patient, caregiver, pharmacist, or other medical practitioner (eg, behavioral counseling, physical therapy, and dietary counseling). The prescription may also include drugs or devices intended for medical diagnosis, surgical treatment, therapy or disease prevention, such as drugs (such as pills or ointments), durable medical devices (such as crutches or stents), implantable medical devices (such as heart rhythms) Regulator or implant), remote medical monitoring device (eg wireless or wired) Health products such as blood glucose/hormone monitors and blood pressure monitors, as well as over-the-counter drugs (such as vitamins and prophylactics). Prescription drugs, in particular, can be classified by chemical composition, route of administration, biological system being targeted, or desired therapeutic effect. The prescription may further include clinical evaluations related to the course of treatment or disease prevention, laboratory tests (such as blood tests and tissue analysis), and diagnostic studies (such as X-ray and magnetic resonance imaging).

Embodiments of the present invention further include new systems and methods for enabling a dispensing office to receive, modify, and report digital prescriptions. The dispensing is a body that "fills" a prescription by providing a prescription for the patient if it is valid and appropriate. A qualified pharmacy is one of the rations, but the ration is not limited to the pharmacy. The rations can also include medical institutions, retail stores, internet or mail order companies, and equipment lenders. Where a legally valid digital prescription is produced at the ration, and the prescription is valid and appropriate, the qualified person employed by the ration (eg, a certified pharmacist) will process the prescription and complete the prescription.

User Branding

In accordance with an embodiment of the invention, the actions that a particular user can take in accordance with a particular digital prescription depend on how the user is "branded" in the system. Each branded user accesses the system based on a pre-assigned title (eg, a card supplier, a licensed pharmacist, a licensed patient, and/or a licensee) and interacts with the digital prescription.

1 is a network diagram in accordance with an embodiment of the present invention. The network diagram of Figure 1 includes There are a number of databases 100 and four types of users: a card provider 101, a card patient 102, a license plater 103, and a licensed pharmacist 104. The branded pharmacist 104 is associated with the ration 105. Each of the branded users can access the user device (such as a mobile device, tablet or computer) and can use the digital database 100 and/or another card through one or more communication networks. The communication is carried out, and the related description will be discussed in detail below.

In accordance with an embodiment of the present invention, the card provider is a user designated in the system to generate a digital prescription for the patient. The authority to generate a digital prescription may be determined by local statutes and practices, especially when the prescription is related to a controlled drug or device. The license provider can be a physician, a physician assistant, a nursing staff, a near-term specialist nursing staff, a dentist, a veterinarian, a clinical pharmacist, an optometry staff, a psychiatrist, a medical psychologist, a hand therapy physician, and the like. In some embodiments, the digital prescription identifies the identity of the branding provider (i.e., the user who generated the digital prescription). This label may be based on the National Provider Identification (NPI) number assigned by the American Medical Association (AMA) or the U.S. Drug Enforcement Administration (DEA) number. In a further embodiment of the invention, the card provider may modify, update, terminate and/or share the digital prescriptions in the system. In a particular embodiment of the invention, the digital prescription may include a referral whereby the rating provider may refer the patient to another provider of the brand.

According to an embodiment of the invention, the licensed pharmacist is a prescription specified in the system as indicated by the effective digital prescription (eg, drugs, medical supplies, appliances) Or service) to the user of the patient. The authority to dispense prescriptions may be subject to local laws and practices, especially when related to controlled drugs or devices. In some embodiments, the digital prescription identifies the identity of the branded pharmacist (i.e., the user who is assigned the digital prescription). This indication may be based on the Pharmacist's Representative Number (PRN) and/or the Individual Dispensary Location (IDL) number. In a further embodiment of the invention, the licensed pharmacist can modify the digital prescription by, for example, reducing the number of remaining renewals associated with the digital prescription. In accordance with local statutes and practices, a licensed pharmacist may modify a digital prescription for a drug version of a drug, and a generic version of the drug (and/or vice versa) . In an additional embodiment, the pharmacist can receive electronic payment for health care information and/or prescription via the same system.

In accordance with an embodiment of the invention, the branded patient is a user in the system designated to be prescribed by a valid digital prescription. The medical services sought by the patient may include medical, dental, surgical or other treatments. In some embodiments of the invention, the digital prescription generated on behalf of the branded patient is labeled with the identity of the branded patient. The foregoing indication may be based on a Social Security Number (SSN) and/or a unique Medical Record Number (MRN). In a further embodiment of the invention, the digital prescription is labeled with a diagnostic code. Diagnostic codes can be obtained, for example, from the World Health Organization's International Classification of Disease Statistics and Classification of Deaths, particularly the ICD-9 and ICD-10 code groups.

In accordance with an embodiment of the present invention, a license holder is a user of the system designated to manage the care of a licensed patient. Regarding the inability to appoint a licensee or need Non-limiting examples of patients designated by the licensee on their behalf include: minors, the elderly, people with reduced mobility, and animals. The authority to manage patient care, especially the acquisition and management of controlled drugs or devices, may be subject to local laws and practices. For example, a caregiver may be authorized by a court when the patient is deemed incapable of managing his/her own care. Alternatively, the licensed patient may appoint a license holder. In some embodiments, the digital prescription identifies the identity of a licensed caregiver (which can be used to represent a patient). This indication can be based on a Social Security Number (SSN) or another unique identifier.

Generation and management of digital prescriptions

The implementation method of the digital prescription is a digital type to indicate the request of the medical provider to open. In accordance with an embodiment of the present invention, a digital prescription has the same information and effectiveness as a conventional paper prescription or a fax prescription produced by CPOE, the difference being encoded in a digital prescription and maintained in an electronic format.

In some embodiments, the digital prescription is encoded and shared as a barcode image. The bar code system has been adopted for many distribution offices, where the product is marked with one-dimensional (1-D) barcode or two-dimensional (2-D) barcode image, which is beneficial for inventory tracking and checkout efficiency. Similarly, most providers and patients have access to hardware and software with the ability to generate and/or read barcodes. Barcode images can be shared via electronic visual displays (such as mobile device screens or cash register screens), printed on paper (for example via an interactive multimedia kiosk or via a cashier receipt printer), or via communication A network (such as the Internet or a cellular network) is transmitted. Barcode images can be used with cameras or scanners, as well as for analyzing cameras or scanners The decoder of the provided image data is read. For example, most mobile devices have cameras that can read bar codes, especially two-dimensional bar codes that have been optimized for cell phone cameras or other cameras that do not have autofocus.

In a preferred embodiment, the digital prescription is encoded and shared by an optimized two-dimensional barcode, such as a 2D Quick Response (QR) Code, a micro QR Code, and a data matrix. (Data Matrix), PDF417 barcode or micro PDF417 barcode. Compared to line type barcodes, action bar codes have, for example, a large amount of data capacity, and high speed and 360 degree reading can be achieved regardless of whether or not an auto focus camera is used. In addition, the action bar code provides high-density recording based on language efficiency, linking functionality, easy encryption, and making the symbol more resistant to deformation, dirt and damage. For an international standard for defining the requirements for action bar codes, reference is made to ISO/IEC 18004:2006, which is incorporated herein by reference in its entirety.

In some embodiments, the digital prescription is encoded and shared in an optical machine readable form of any material (eg, using optical character recognition or a disc or tape). In some embodiments, the digital prescription is encoded and shared using a character encoding scheme (eg, ASCII or Unicode). In still further embodiments, the digital prescription is encoded and shared by magnetic media, such as (disk, tape, magnetic ink or magnetic strip), semiconductor, floating gate crystal (eg, flash memory), radio transmission (eg radio frequency identification (RFID) tags, near field communication (NFC) tags or Bluetooth technology).

By coded fields (such as patient status and remaining renewals) After a digital prescription is generated, the card provider can allow the licensed patient and/or the licensee to maintain a digital record while effectively obtaining a prescription, and to obtain a digital number with an unfilled balance when renewable. Prescription 笺. In some embodiments, the digital prescription will evolve with the use. That is, the system can automatically update the field based on the event, or allow authorized card users to modify the field. The fields that can be updated or modified in the derivative digital prescription are dynamic fields. In a further embodiment, the system may include a dynamic network database or other data structure that automatically receives and updates information related to the digital prescription in the network, and each digital prescription code is included in the code. A digital link to a database (such as a Uniform Resource Locator (URL)).

For example, in some embodiments, when a licensed pharmacist dispenses a prescription associated with a digital prescription, the system can automatically update the dynamic field of the derived digital prescription to indicate that the digital prescription has been dispensed. Additionally, when the digital prescription is used for renewal, the system can automatically update the dynamic field representing the remaining renewal amount in a deductive manner each time the renewal is obtained by the patient or caregiver. Alternatively, the licensed pharmacist can manually modify the dynamic field of the digital prescription to indicate that the digital prescription has been dispensed, to identify the licensed pharmacist who is fitted with the digital prescription, and/or to deduct the remaining renewal amount. Likewise, in some embodiments, the card provider may take the automatic update or manually modify the digital prescription, such as increasing the number of remaining renewals to update the digital prescription, or canceling the remaining renewal amount to terminate the digital prescription.

According to some embodiments, after the digital prescription is generated, the system can maintain a static field that cannot be modified by any of the branded users. For example, at the digital place The static field of the box may include the identity of the branding provider that generated the prescription and/or the identity of the branded patient on behalf of the digital prescription. A field modified by only one type of branded user is a dynamic field for the type of card user, but it can be a static field for all other types of card users. Similarly, a field that is modified only for a particular branded user is a dynamic field for that particular card user, but can be a static field for all other card users.

In some embodiments, an event or modification caused by an authorized branded user may cause the system to change the dynamic field to a static field. For example, in accordance with some embodiments, once the system updates or modifies a dynamic field of a digital prescription to identify a licensed pharmacist who is aligning the digital prescription, the dynamic field can become a static field to enable the The identity of the licensed pharmacist can be maintained in the history of the derivative digital prescription.

In accordance with some embodiments of the present invention, a digital database or other data structure may be used to maintain a digital prescription and other medical records of the patient. The digital database can be implemented using a proprietary or open source database platform. In a preferred embodiment, the digital database is a dynamic online repository accessible by a network (e.g., the Internet). Some embodiments may use the network database management system that includes, such as ^{MySQL TM (Oracle Corp., Redwood Shores} , CA), SQL Server ® (Microsoft Corp., Redmond, WA) or DB2 ^® (IBM Corp., Armonk, NY). In an alternate embodiment of the present invention, digital prescriptions and records can be stored or organized into a non-database data structure (eg, a distributed hash table) or a hybrid of partial database functions. Data structure (eg DynamoDB (Amazon Web Services, Inc., Seattle, WA)).

In some embodiments, the digital database or other data structure is a cloud-based repository. The above-mentioned cloud infrastructure and service management and/or hosting can be selected from one or a mixture of the following deployment models: private, community or public. Cloud service providers such as Amazon Web Services, Inc. (Seattle, WA), Windows Azure ^TM Cloud Services (Microsoft Corp., Redmond, WA), Google Cloud Platform (Google, Inc., Mountain View, CA) or Rackspace ^® (San Antonio, TX), etc., can be used to access cloud infrastructure and services.

According to an embodiment of the invention, the digital database or other data structure is hosted by a server having a network (eg, internet) access function, so the digital prescription and record can be different for multiple licensed users. User equipment (UE) device to obtain. The server can be purchased or rented through a network (internet or cloud) hosting service. The server may actually contain more than one server and employ more than one server protocol. The server can be a database server or a server (ie, a web server) that can provide database services and other services, such as connecting to an HTTP client to transmit commands and receive responses and/or data.

Some embodiments of the present invention are designed to comply with local regulations regarding the control of private information and/or health information exchange. In a preferred embodiment, the digital database or other data structure is in accordance with the standards set forth by the US Health Insurance Portability and Accountability Act (HIPAA). All information is transmitted between the licensed users, Incoming and mutual transfer. In a further embodiment, the system is automatically updated in accordance with regulatory changes (e.g., HIPAA adjustments).

The digital database or other data structure maintains a history of deriving digital prescriptions, including access logs. In some embodiments, the card provider can customize the alert service (eg, via email, short message service (SMS), or push notification) and alert the user to the digital data based on the preset alert preferences. Updates in the library or other data structure (such as updates to digital prescriptions).

In some embodiments, the card user can access the digital database or other data structure through an interface (eg, a graphical user interface (GUI)) through a prescription management software application. And interact with it. The card user can list or select preferences. For example, the branded patient 102 may list or select a primary care physician (eg, a branding provider 101), a preferred ration (eg, ration 105), and an authorized caregiver (eg, a licensee 103). The branded patient 102 can also disclose known health problems such as allergies (e.g., to food or drugs), completed procedures (e.g., hemophilia), and chronic conditions (e.g., diabetes). The licensed patient 102 can even upload and store insurance or payment information. The medical records of all of the above patients can be stored in a digital database and accessed by authorized card users via the prescription management software application.

According to an embodiment of the invention, the prescription management software application is hosted on a server having a network (eg, internet) access function, thereby enabling digital prescription and recording to utilize different UE devices for multiple licensed users. Come to get. The servo The use of the device can be purchased or rented through a network (internet or cloud) hosting service. The server may actually include one or more servers and employ more than one server protocol. The server may be a web server or a server (eg, a database server) for providing database services and other services.

Digital prescription security and privacy

In some embodiments of the invention, the digital prescription may be encrypted to prevent a person other than the authorized branded user from decrypting the prescription. Similarly, access to centralized digital databases can be regulated. System security maintenance and the integrity and concealment of the encoded information in each digital prescription can be achieved through various encryption or authorization schemes. For example, the scheme may include symmetric-key cryptography algorithms, public-key cryptography algorithms, or some hybrid encryption algorithms.

In some embodiments, the encryption algorithm described above is a cipher, such as a data encryption standard, a triple data encryption standard, or a near-order encryption standard. In a preferred embodiment, a fixed-length string of plaintext bits of a block size, such as 64 bits or a multiple thereof (eg, 128 bits or 256 bits), is encrypted to yield the same size. The string of bits. The block size can be any power of 2 to generate an encrypted string of the same size. The algorithm uses a 64-bit key (or, for example, a 128-bit key or a 256-bit key, etc.) generated in a unique manner, via a series of displacements of a hexadecimal number of defined length. Generate several subkeys. The plaintext bit is first permuted to change the position of each bit in the string. This modified string will then be divided into the same size Two halves. The algorithm combines a particular subkey with the first half of the string and performs a non-linear transformation via the substitution of a preset data table. After each non-linear transformation, the half of the converted string is combined with the second half of the string. The recombined 64-bit string undergoes another permutation and is again divided into two halves of the same size. The above process is repeated using different subkeys. The number of subkeys determines the number of processing stages, and the number of processing stages determines the strength of the encryption. After the above processing stages are completed, the recombined 64-bit string undergoes a reversal to return to the initial permutation and draws a period for the encryption process. As long as the original 64-bit key is known, it can reverse the above algorithm and decrypt the data.

Due to the sensitive nature of medical information, access control is quite important to all embodiments of the present invention. For example, in some embodiments, one or more third party groups (eg, credential agencies) may be defined to issue and validate credentials (eg, Public Key Infrastructure (PKI) digital credentials) to all The card user associated with the digital prescription. Each credential is unique and uses a digital signature to allow the public key to be combined with the branded user. The third party community combines its credentials with the public key to verify the certificate chains, thereby authorizing the identity to each of the branded users.

In accordance with some embodiments of the present invention, the different types of card users shown in FIG. 1 individually define different access requirements associated with the digital prescription. For example, after the digital prescription is generated by the branding provider 101, each authorized card user can apply a digital signature to record and update the derivative digital prescription in the digital database 100. In a particular embodiment, the card provider 101 can have a digital signature The prescription is simply transmitted to the digital repository 100 via the communication network and/or transmitted directly to the licensed patient 102 or the license holder 103 to automatically record the generation of the digital prescription.

According to some embodiments, the licensed patient 102 and the license holder 103 are only allowed to view and share the digital prescription. However, similar to the branding provider, the carding patient 102 or the licensee 103 can simply view the prescription of the digital signature via the communication network to automatically record access to the digital prescription. Alternatively, the card patient 102 or the licensee 103 can cause the prescription with the digital signature to be transmitted to the digital database 100 via the communication network and/or directly to the licensed pharmacist 104 of the ration 105. Automatically record access to digital prescriptions.

After the prescription dispensing, the licensed pharmacist 104 can transfer the prescription with the digital signature from the point-of-sale terminal to the digital database 100 via the communication network, thereby recording the digital prescription system. Served or fully matched. For each event, the third party community can verify the identity of the authorized user and increase the record to the digital prescription access log and prescription history of the patient in the digital database 100 as soon as the derivative digital prescription is active.

In a further embodiment of the system, the licensee is required to provide one or more of the following credentials: a personal message (eg, a password, a Personal Identification Number (PIN), or a CAPTCHA phrase). ), physical objects (such as access cards or mobile devices), and biometrics (such as dactyloscopy, retinal scan, or voice recognition) to exclude unauthorized users.

Implementation of a system based on digital prescription

Embodiments of the invention may be implemented in a variety of configurations, such as hardware, software, firmware, or a combination thereof. In some embodiments, the modules are presented in software and executed as an application for user equipment (UE). The user device can include a mobile phone, a wireless communication capable notebook, a netbook, a smart phone, or any other wireless device. The user device may also cover many other devices, such as televisions (TVs), video projectors, set-top boxes or on-board units, digital video recorders (DVRs), computers, netbooks, notebook computers, or any other An audio/video device that communicates with the network.

2 is a schematic diagram of a user device 201 for generating, modifying, and sharing a digital prescription in accordance with a particular embodiment of the present invention. The user equipment 201 can include a central processing unit (CPU) 202, a data machine 203, a network interface selection module 204, one or more memory devices 205, one or more user interfaces 206, and one or more interfaces. Transceiver 207 of 208.

The central processor 202 executes the program performed by the user device 201. The user device can be provided with one or more processors to process instructions and execute software that can be stored in the memory. In some embodiments, the software required for program or database implementation includes a high-level programming language or an object-oriented language (eg, C, C++, C#, Java, or Perl). If necessary, the software can also be implemented in a combination of languages. The packet program implemented in the user device can include any program defined by its content. For example, the packetization process may involve high-level data link control (HDLC) framing, header compression, and/or encryption. The processor can Any suitable processor that combines a central processing unit, application processor, and memory. Suitable processors may include any microprocessor (single or multi-core), system on chip (SoC), microcontroller, digital signal processor (DSP), graphics processing unit (graphics processing Unit, GPU), combined hardware and software logic or any other integrated circuit that can process instructions.

In some non-limiting embodiments, the program performed by the user device 201 can include encoding to create or modify a digital prescription, encrypting to secure a digital prescription, decoding/decrypting to access a digital prescription, and confirming a card. The identity/permission of the user and the transaction to obtain/distribute the prescription.

The data machine 203 is configured to be based on, but not limited to, one or more of the following communication standards: WLAN-related standards, such as 802.11 (such as 802.11a, 802.11b, and/or 802.11g) and standards for mobile communications. For example, it is defined under 3GPP and 3GPP2 to implement modulation and frame formation of signals.

The user device 201 can utilize multiple access technologies to communicate with multiple radio networks and wired communication networks. The network interface selection module 204 selects a network interface to receive network services. The network interface selection module 204 can communicate with different types of communication networks including, but not limited to, mobile communication networks (eg, 2G, 3G, 4G, and LTE) and WLANs. In some embodiments, the network interface selection module 204 can select the network interface by analyzing data load information associated with the available interfaces. In these embodiments, the network interface selection module 204 can be configured to attach to process a minimum amount of data traffic and/or have more Use the network interface of resources. In a further embodiment, the network interface selection module 204 can also determine which network interface to connect to by analyzing additional information. The network interface selection module 204 can be implemented in a hardware form using a specific application specific integrated circuit (ASIC), a programmable logic array (PLA), or any other integrated circuit. The network interface selection module 204 can also be implemented in a software form using the memory device 205.

The user device has one or more memory devices 205, such as a non-transitory computer readable medium, a flash memory, a disk drive, a CD player, and a programmable read only Programmable read-only memory (PROM) and/or read-only memory (ROM). The one or more memory devices 205 can also store instructions that are executed by the central processor 202 for use in the above described programs. The one or more memory devices 205 can store information of the licensed users, including static data and/or dynamic data input by the user.

The one or more user interfaces 206 provide input and/or output mechanisms to communicate with users of the user device. A user of the user device transmits a digital prescription to/from the user device 201 via the one or more user interfaces 106. The one or more user interfaces 206 can be implemented in hardware or software. The one or more user interfaces 206 can be used to receive data and control information from the network as well as from local resources. Input devices for preserving digital prescriptions may include, but are not limited to, bar code readers, image scanners, and cameras. Meanwhile, an output device for transmitting and/or sharing a digital prescription cartridge may include But not limited to, screens, touch screens, monitors, and printers. Other input/output devices may include, but are not limited to, the data machine 203, the transceiver 207 having the interface 208, a keyboard, a microphone, a speaker, a pen device, a trackball, a trackpad, and a mouse. The one or more user interfaces 206 can operate under a plurality of communication protocols. In some embodiments, the one or more user interfaces 206 are implemented by software, while in other embodiments, the one or more user interfaces 206 are implemented in hardware and transmitted and received. The device 207 transmits and receives signals via a variety of media (eg, optical, copper, wireless, etc.).

The one or more transceivers 207 each include a transmitter and a receiver. The transmitter and receiver can be integrated into a single wafer or can be implemented in multiple independent wafers, or even integrated with central processor 202 and/or one or more memory devices 205. In some embodiments, the one or more transceivers 207 include a plurality of interfaces (hereinafter collectively referred to as interfaces 208) for providing input and/or output mechanisms for interfacing with other network devices (eg, by other licensed users) The user equipment of the operation communicates. In some embodiments, the interface 208 measures and outputs the wireless signal strength (eg, base station and access point) of the wireless interface. The interface 208 can be implemented in a hardware form and transmit or receive signals through a variety of media (such as, but not limited to, fiber optic lines, copper wire, wireless, etc.), and wherein the plurality of different protocols can be non-transitory (non- Transient).

In some embodiments, the user device is a smart phone and has advanced capabilities such as word processing, web browsing, electronic games, e-books, operating systems, and full keyboards. The operating system executable by the user device, such as Symbian OS, Apple iOS, Blackberry OS, Windows Mobile, Linux, Palm WebOS And Android. The screen can be a touch screen to input data to the user device instead of the full keyboard. The microphone and voice recognition software can also be used to input data to the user device. The user device can have the ability to execute an application or to communicate with an application provided by a server in a communication network. The user device can receive updates or other information from the application on the network. The user device can also save global positioning coordinates or other location information in its push or memory.

Although the above systems and methods are mainly described with mobile devices, the generation, management, and sharing of digital prescriptions can also be performed by fixed devices and fixed frequency bands, such as using wired networks (or wirelessly connected lines, such as WLAN) Personal desktop, computer kiosk or point-of-sale terminal. It is well known that in the case of a WLAN system, a user station communicates with an access point to communicate with other individuals over the Internet.

Example of use of a system based on digital prescription

3 is a flow diagram of a system for generating, managing, and sharing digital prescriptions in accordance with an embodiment of the present invention, in accordance with an embodiment of the present invention. To generate a digital prescription for a given card patient, the card supplier identifies the patient in step 301 and retrieves the static data 302 associated with the patient. The static data 302 may include, but is not limited to, prescription materials, command sets, prescription interaction data, customized medical instructions, diagnostic codes, patient data, caregiver data, provider data, pharmacist data, rations data, extracted from Existing digital prescription data, insurance data, payment data, new digital prescriptions, production records, existing digital prescriptions, revisions, digital prescriptions, and remaining renewals.

The command group is a series of preset prescriptions that the card provider provides for a particular session. Customized medical instructions associated with the prescription can be tailored to a particular branded patient. The diagnostic code can be specified by the provider or taken from, for example, an ICD code set. Patient data may include identification data for the branded patient (eg, social security number or unique medical record number), contact information, and treatment information. The caregiver information may include identification information (eg, a social security number or another unique identification number), contact information, and relationship information for the licensee. The provider profile may include identification information of the branding provider (eg, National Provider Identification and/or US Drug Enforcement Administration number), contact information, and practice information. The pharmacist and/or rations information may include identification information (eg, pharmacist representative number and/or personal ration location number) and contact information for the licensed pharmacist and/or rations.

Next, the card provider selects the static data 302 and/or the dynamic data 303 in step 304. Dynamic data 303 may include, but is not limited to, prescription materials, command sets, prescription interaction data, customized medical instructions, diagnostic codes, patient data, caregiver data, provider data, pharmacist data, rations data, extracted from Existing digital prescription data, insurance data, payment data, new digital prescriptions, production records, existing digital prescriptions, revisions, digital prescriptions, and remaining renewals.

In step 305, the selected static data 302 and/or dynamic data 303 are combined to generate a new digital prescription or to modify an existing digital prescription. In step 306, the digital prescription is encoded and represented in a machine readable form, such as a QR Code. In step 307, the encoded digital prescription 笺 Encryption can be performed using one or more encryption algorithms to control access to the above-described basic data, thereby protecting the privacy and integrity of the digital prescription when transmitted between authorized card users.

In step 309, the card supplier, after being encoded and/or encrypted, shares the digital prescription by outputting the digital prescription (eg, directly to another branded user). In other examples, the card provider may, for example, store the digital prescription in a local memory device or a centralized digital database (which may be the licensed patient, any licenseor, and any The digital pharmacist selects the method to selectively store the digital prescription (either before or after the output of step 308, even replacing the output). Using an embodiment of a common digital database, the user's access and the instant history of the digital prescription can be monitored/recorded.

4 is a flow chart of a network for generating, managing, and sharing a digital prescription, according to an embodiment of the present invention, in accordance with an embodiment of the present invention. The licensed patient does not receive the digital prescription directly from the custom card provider, or retrieves the stored digital prescription from the general digital database. Since the licensed patient is only allowed to access and cannot modify the digital prescription, the prescription is a static data 401.

In some embodiments, as shown in step 402, the carding patient may choose to add additional information to the digital prescription. Such information may include other static data 401 (such as insurance or payment information) and/or dynamic information 403 (such as the number of prescriptions requested or information about discounts, coupons or reward schemes). In some embodiments, a combination of insurance options and/or stored payment options available for the selected patient may include, but Not limited to, credit cards, debit cards, Health Savings Accounts, Federal Savings Accounts, checking accounts, deposit accounts, PayPal® or any other remittance account that can be used for wire transfer payments. In a further embodiment, the payment option may also take into account activities such as discounts, coupons or sweepstakes.

Next, in step 404, the static data 401 and/or the dynamic data 403 are combined to expand the existing digital prescription. In step 405, the derivative digital prescription is encoded into a machine readable form. In step 406, the encoded digital prescription may be encrypted to limit access and/or modification rights to a particular authorized user.

According to still further embodiments, the branded patient shares the derived digital prescription by using a derived digital prescription output that is encoded and/or encrypted in step 408. In output step 408, the direct transfer digital prescription is associated with another branded user. In other embodiments, the branded patient may by way of, for example, storing the digital prescription in a local memory device, or copying the digital prescription from a local memory device to a general digital database (which may be a licensed card) The pharmacist can access the patient's consent to store the digital prescription (or the output can be replaced before or after the output of step 407).

Using an embodiment of a general digital database, the user's access can be monitored and the instant history of accessing the digital prescriptions can be recorded, and the authorized users with access rights can access the instant history. These or other embodiments may also cause a particular branded user to be notified of a new or updated digital prescription via any suitable means of communication (eg, email, short message service (SMS), and push notification). Hey.

In an exemplary embodiment, the carding patient uses this procedure to establish a request to renew a prescription that has previously been assigned to a patient based on a digital prescription, ie, a Request For Prescription (RFP). In a preferred embodiment, a licensed patient can use this procedure to simultaneously dispense more than two digital prescriptions. However, when the relevant digital prescription appears to have a risk of adverse or dangerous interactions between two or more prescriptions, an alert or other action may be taken.

FIG. 5 is a flow chart of a network for generating, managing, and sharing a digital prescription according to an embodiment of the present invention in the perspective of a licensed pharmacist. In step 501, the licensed pharmacist retrieves the digital prescription from the general digital database, or directly receives the digital prescription from the licensed patient, the license provider or the license holder. In step 502, the licensed pharmacist extracts the information needed to dispense the prescription by decrypting and decoding the digital prescription. This information may include, but is not limited to, the original digital prescription, as well as insurance information, payment information and any other static and/or dynamic information provided by the user. When the licensed pharmacist is able to access and view the necessary information, in step 503, the licensed pharmacist may assign the prescription to the licensed patient and/or the licensed licensee to match the digital prescription. .

In a particular embodiment, step 502 or step 503 itself or its concept is to cause the pharmacist representative number of the licensed pharmacist to be added to the field in the prescription or to complete the existing field, recorded as a derivative digital prescription. a part. Since the licensed pharmacist is only allowed to modify a particular field associated with the derived digital prescription, the remaining remaining fields can be considered static data 504. In some embodiments, as shown in step 506, the licensed pharmacist may choose to add additional information to the digital prescription. The amount External data may include other static data 504 (such as insurance or payment information) and / or dynamic data 505 (such as the number of drugs requested, the replacement of a pharmaceutical drug with a generic drug (or its reverse) or about discounts, coupons) Or reward program information).

Next, in step 507, the static data 504 and/or the dynamic data 505 are combined to expand the existing digital prescription. In step 508, the derived digital prescription will be encoded into a machine readable form. In step 509, the encoded digital prescription may be encrypted to restrict access and/or modification rights to a particular card user.

According to still further embodiments, in step 511, the licensed pharmacist shares the derived digital prescription by a derivative digital prescription output based on encoding and/or encryption. The step of inputting in step 511 can include directly transferring the digital prescription to another branded user. In other embodiments, the branded patient and/or the licenseor may, for example, store the digital prescription in a local memory device or copy the digital prescription from a local memory device to a general digital database. The method (which may be accessed by the licensed pharmacist with the consent of the branded patient and/or the licensee) to store the digital prescription (or even before or after the output of step 510) The output).

Using an embodiment of a general digital database, the user's access can be monitored and the instant history of accessing the digital prescriptions can be recorded, and the authorized users with access rights can access the instant history. These or other embodiments may also cause a particular branded user to be notified of a new or updated digital prescription via any suitable means of communication (eg, email, short message service (SMS), and push notification). Hey.

In some embodiments, the user can register as a card supplier, a branded agent Division, card patient or license holder. A user can access the network as multiple card users, however, in some embodiments some of the tag types can only be registered once. For example, a provider may not be registered as a licensed patient after being registered as a license provider and becoming a licensed patient at the same time. However, in some embodiments, the provider may be allowed to register as a license provider multiple times, and each account represents a different (eg, hospital versus private) practice.

FIG. 6 is a flow chart of a user's carding according to an embodiment of the invention. In step 601, the user uses the carding program by registering or accessing a system on the user's equipment (a tablet, a smart phone, a desktop computer, or a portable computer with an internet connection).

For security reasons, the user may be asked to select a unique set of personal identification codes during the registration process. Additional information can be collected to prevent the user from forgetting or needing to reset the personal identification number. The user can also specify a unique set of identification numbers (IDs). In some embodiments, the identification code can be generated via a random generator. In some embodiments, the identification code is an existing identification code, such as a social security number, a driver's license number, an insurance policy number, or a phone number.

According to step 602, the user must enter the correct personal identification code and/or identification code to access the network. If the personal identification code and/or the identification code matches the record of the particular user, in step 603, the user is branded and awarded a set of related to the generation, access, modification and sharing of the digital prescription. Specific permissions. In step 604, the network interface reflects the type of the card.

7A-7C illustrate a card user in accordance with an embodiment of the present invention. A flow chart of the number of prescriptions. 7A-7C are exemplary use cases illustrated for the network depicted in FIG. 1. FIG. 7A illustrates the flow of a digital prescription, the digital prescription being transmitted from the order provider 101 to the named patient 102 and the license holder 103 via the digital database 100. The user interface of the digital database 100 allows the patient 102 and/or caregiver 103 to access and view changes in the patient's digital prescription.

FIG. 7B depicts a schematic diagram of the caregiver 103 requesting renewal of authorization from the provider 101 upon obtaining permission from the patient 102. This diagram also shows the flow of the renewal authorization, similar to FIG. 7A, through the digital database 100 from the custom provider 101 to the named patient 102 and the license holder 103. The user interface of the digital repository 100 allows the patient 102 and/or caregiver 103 to access and view the renewal authorization.

In the preferred embodiment, the licensed patient authorizes the licensee by inviting the licensee to connect to the network profile or by accepting the licensee's invitation to link to the network profile. The licensed patient may also cancel the authorization of the licensee, in which case the licensee will not be able to access the network profile of the licensed patient again. In some embodiments, the previous caregiver will be recorded as part of the patient's medical record.

FIG. 7C is a schematic diagram showing the digital prescription being transmitted through the digital database 100 to obtain a prescription. For example, patient 102 may travel to a rations 105 having an internet to obtain a prescription using a digital prescription. The patient 102 uploads the digital prescription to the digital database 100 and the pharmacist 104 retrieves the digital prescription. After the pharmacist dispenses the prescription by dispensing the prescription, the digital database is updated to allow each of the branded users to access the instant information associated with the valid digital prescription. When the number of remaining renewals is zero, the digital prescription will be classified as completed and archived In the prescription history of the branded patient. Unless the card provider has further action, the licensed pharmacist cannot match the digital prescription filed.

FIG. 8 is a flow chart of terminating a digital prescription in accordance with an embodiment of the present invention. Unlike previous methods or systems, embodiments of the present invention allow for multi-directional flow of digital prescription related information. Some embodiments allow the card supplier to interact with the digital prescription even if the prescription has been passed to other branded users.

In Figure 8, a general digital database may or may not be present in accordance with an embodiment of the present invention. From step 801, the first provider 101 generates a digital prescription and transmits the prescription to the patient 102 and/or caregiver 103. In step 802, the patient 102 and/or the caregiver 103 present the derivative digital prescription to the pharmacist 104 at the ration 105 (dispensing the prescription to match the digital prescription). In step 803, the patient presents the second provider 106 with medical information including a valid digital prescription and a prescription history. When the second provider 106 confirms that the patient 102 needs to change, replace, and/or deactivate a particular prescription, the second provider 106 can modify or terminate the associated digital prescription.

The card issuer may use such functionality to modify or terminate the digital prescription generated by the provider, or to modify or terminate the digital prescription generated by another provider treating the same licensed patient. Such modification and/or termination functions can be used, for example, to nullify a non-essential location to prevent undesirable prescription interactions or to avoid undesirable side effects. In some embodiments, the termination function is accomplished by simply reducing the number of remaining refills in the digital prescription to zero and archiving the prescription.

According to some embodiments of the present invention, when such a modification or termination function is used on a digital prescription, the provider who originally generated the digital prescription will be notified The reason. In step 804 of FIG. 8, the first provider 101, the patient 102 and/or the caregiver 103, and the pharmacist 104 are notified by the second provider 106 regarding the modification or termination of the derivative digital prescription. . If there are any questions or concerns, the first provider 101 will use the system to communicate with the second provider 106 and even overwrite the termination function for the digital prescription.

According to an embodiment of the present invention, FIG. 9A and FIG. 9B use two screenshots to display a web interface screen display of an exemplary user equipment UE900 having functions of digital prescriptions 901 and 902, respectively. As shown in Figure 9A, the digital prescription 901 contains information from the party requested by the medical provider. As shown in FIG. 9B, the digital prescription is encoded into a machine readable 2D barcode 902 which, after optimization, can be captured by a camera that does not have auto focus (such as a mobile phone with only a conventional camera built in). In some embodiments, when the branded patient and/or the licenseor receives the digital prescriptions 901 and 902, a screen image similar to any of FIGS. 9A and 9B is displayed on the card. Patient and/or user equipment UE900 of the licensee.

In some embodiments of the invention, the carding user accesses and interacts with the system via a prescription management software application. The app automatically uploads new and/or modified data to a dynamic online database or other data structure. For example, a licensed patient and/or a licensee may use a prescription management application (eg, a graphical user interface with a specific directory in a dynamic online database) to illustrate via either of FIGS. 9A and 9B. A similar picture image is used to view and/or output a valid digital prescription. The prescription management application further provides the ability of the licensed patient and/or the licensee to navigate the patient's prescription history or other stored medical records. In a preferred embodiment, the prescription management application outputs a machine readable digital prescription having a human readable place name or a common name. In some embodiments, the prescription of the drug is identified using a unique and three-segment numbered National Drug Code (NDC), which is a generic product identifier assigned by the Food and Drug Administration (FDA) for human use. . The use of national drug codes can improve the tracking of patient prescription history and the identification of potential drug interactions.

Similarly, FIG. 10 uses screenshot 1000 to illustrate a web interface display having a graphical user interface function of a recipe management application in accordance with an embodiment of the present invention. The card issuer can use, for example, a screen image similar to screenshot 1000 and linked to a particular directory in the dynamic online database to generate and manage multiple digital prescriptions for multiple patients. In a further embodiment, the card provider can view, modify, and/or terminate the digital prescription provided to his or her patient but provided by another branding provider. In this manner, in accordance with embodiments of the present invention, access to the system can be somewhat open to the card provider while at the same time closing or limiting other card users.

Those of ordinary skill in the art will understand that the present disclosure can be practiced in other ways than the specific disclosure described above. The particular embodiments described above are therefore considered as illustrative and not restrictive. Those skilled in the art will recognize, or will be able Therefore, the scope of the invention should be construed as being limited by the scope of the appended claims and the equivalents thereof.

100‧‧‧Digital Database

101‧‧‧First Provider

102‧‧‧ patients

103‧‧‧ caregivers

104‧‧ ‧ pharmacist

105‧‧‧ Distribution Office

106‧‧‧second provider

801‧‧‧New digital prescription笺

802-803‧‧‧Steps

804‧‧‧Modified or terminated digital prescription笺

Claims (37)

An electronic prescription system for generating, managing, and sharing a digital prescription, comprising: a processor for processing data about a digital prescription, the data including dynamic data and/or static data; and a storage medium for storing the digital prescription Information that can be executed by the processor, the instructions being executed to cause the processor to: merge the selected portions of the dynamic data and/or the static data to establish the digital prescription; and apply for security The program goes to the digital prescription to establish a digital prescription. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, wherein the security procedure includes encoding the digital prescription. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, wherein the security procedure includes encrypting the digital prescription. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1 of the patent application, further comprising an output device for outputting the security procedure. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 4, wherein the security digital prescription is output to a designated brand user. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 5, wherein the designated card user includes one or more of a patient, a provider, a pharmacist, and a caregiver. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 4, wherein the security digital prescription is output to a storage device. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, further comprising instructions executable by the processor, the instructions being executed to cause the processor to store the security digital prescription Go to the storage medium. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, further comprising: an interface for communicating with a network database in a computer network; and instructions executable by the processor When the instruction is executed, the processor requests the dynamic data and/or the static data through the interface to the network database. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, further comprising: an interface for communicating with a network database in a computer network; and instructions executable by the processor When the instruction is executed, the processor outputs the saved digital prescription to the network database via the interface. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, wherein the static data may include one or more of the following: prescription materials, command sets, prescription interaction materials, and customizations. Medical instructions, diagnostic codes, patient data, caregiver data, provider information, pharmacist data, rations data, data extracted from existing digital prescriptions, insurance data, payment data, new digital prescriptions, production records, existing digital prescriptions笺Modification, digital prescription The record and the number of remaining renewals are displayed. An electronic prescription system for generating, managing, and sharing a digital prescription as described in claim 1, wherein the dynamic data may include one or more of the following: prescription materials, command sets, prescription interaction materials, and customizations. Medical instructions, diagnostic codes, patient data, caregiver data, provider information, pharmacist data, rations data, data extracted from existing digital prescriptions, insurance data, payment data, new digital prescriptions, production records, existing digital prescriptions笺 Modifications, digital prescriptions, matching records, and remaining renewals are displayed. An electronic system for generating, managing, and sharing digital prescriptions, comprising: an interface for communicating with a computer network; a processor for processing information about a digital prescription, the data including dynamic data and/or static data; Means for storing information about the digital prescription; and instructions executable by the processor, the instructions being executed to cause the processor to: receive a security digital prescription via the interface; and extracting from the digital prescription The selected portion of the dynamic data and/or the static data. An electronic system for generating, managing, and sharing a digital prescription as described in claim 13, wherein the instructions for extracting the selected portion include instructions for decoding the secured digital prescription. An electronic system for generating, managing, and sharing a digital prescription as described in claim 13 wherein the instructions for extracting the selected portion include In order to decrypt the instructions for the preservation of the digital prescription. An electronic system for generating, managing, and sharing a digital prescription as described in claim 13 wherein the selected portion is selected by a designated brand user. An electronic system for generating, managing, and sharing a digital prescription as described in claim 13 of the patent application, further comprising instructions executable by the processor, the instructions being executed to cause the processor to store the extracted data Describe the selected part. An electronic system for generating, managing, and sharing a digital prescription as described in claim 17, wherein the selected portion is stored in the storage medium. An electronic system for generating, managing, and sharing digital prescriptions as described in claim 17, wherein the selected portion is stored in a network database. A method of generating, managing, and sharing a digital prescription in an electronic prescription system, comprising: selecting information about a digital prescription, the data including dynamic data and/or static data; and combining the dynamic data and/or the static data The selected portion is used to establish the digital prescription; and the security procedure is applied to the digital prescription to establish a digital prescription. A method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, wherein the security procedure includes encoding the digital prescription. A method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, wherein the security procedure includes encrypting the digit Prescription 笺. The method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, further includes outputting the security procedure. A method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 23, wherein the security digital prescription is output to a designated brand user. A method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 23, wherein the secured digital prescription is output to a storage device. The method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, further comprising storing the preservation program in the storage medium. The method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, further comprising: accessing the network via an interface for communicating with a network database in a computer network The database requests the dynamic data and/or the static data. The method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, further comprising: accessing the network via an interface for communicating with a network database in a computer network The database outputs the security digital prescription. A method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, wherein the static data may include the following One or more: prescription data, command set, prescription interaction data, custom medical instructions, diagnostic code, patient data, caregiver data, provider information, pharmacist data, rations data, extracted from existing digital prescriptions Data, insurance data, payment information, new digital prescriptions, production records, existing digital prescriptions, revisions, digital prescriptions, matching records, and remaining renewals. A method for generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 20, wherein the dynamic data may include one or more of the following: prescription data, a command set, and a prescription interaction data. , customized medical instructions, diagnostic codes, patient data, caregiver data, provider information, pharmacist information, rations data, data extracted from existing digital prescriptions, insurance data, payment information, new digital prescriptions, records, The existing digital prescriptions are modified, the digital prescriptions are matched, and the remaining renewals are displayed. A method of generating, managing, and sharing a digital prescription in an electronic prescription system, comprising: receiving a secure digital prescription via an interface for communicating with a computer network, the secure digital prescription including dynamic data and/or static data And extracting the selected portion of the dynamic data and/or the static data from the digital prescription. A method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 31, wherein the step of extracting the selected portion comprises decoding the secured digital prescription. Produced in an electronic prescription system as described in claim 31, A method of managing and sharing a digital prescription, wherein the step of extracting the selected portion includes decrypting the secured digital prescription. A method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 31, wherein the selected portion is selected by a designated brand user. The method of generating, managing, and sharing a digital prescription in an electronic prescription system as described in claim 31, further comprising storing the selected portion of the extracted material. An electronic system for generating, managing, and sharing a digital prescription as described in claim 35, wherein the selected portion is stored in the storage medium. An electronic system for generating, managing, and sharing a digital prescription as described in claim 35, wherein the selected portion is stored in a network database.