WO2014093377A1 - Procédé et système de suivi de marchandises - Google Patents

Procédé et système de suivi de marchandises Download PDF

Info

Publication number
WO2014093377A1
WO2014093377A1 PCT/US2013/074179 US2013074179W WO2014093377A1 WO 2014093377 A1 WO2014093377 A1 WO 2014093377A1 US 2013074179 W US2013074179 W US 2013074179W WO 2014093377 A1 WO2014093377 A1 WO 2014093377A1
Authority
WO
WIPO (PCT)
Prior art keywords
transnomic
code
management server
prescriber
information
Prior art date
Application number
PCT/US2013/074179
Other languages
English (en)
Inventor
Eric Greenman
Bo E.H. SAXBERG
Original Assignee
Itd Holdings, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/710,167 external-priority patent/US9235869B2/en
Application filed by Itd Holdings, Llc filed Critical Itd Holdings, Llc
Publication of WO2014093377A1 publication Critical patent/WO2014093377A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/13—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered from dispensers

Definitions

  • This invention relates generally to a system for tracking pharmaceuticals and implantable devices, and more particularly to a method and system for using a transnomic code to track pharmaceuticals and implantable devices throughout a life-cycle of the same.
  • Figure 1 is a diagrammatic illustration of the general architecture of one embodiment of a transnomic code system of the present invention
  • FIG. 2 is a flow diagram of one embodiment of the transnomic code system process in accordance with the present invention.
  • Figure 3 is a diagrammatic illustration of an embodiment of a transnomic code and illustrates a flow of information among components of the present invention.
  • Figure 4 A-F is a flow diagram of a further embodiment of the transnomic code system process in accordance with the present invention.
  • FIG. 1 illustrates one non- limiting embodiment of the general architecture of a transnomic code system 100 (herein also referred to as "TCS") that operates in accordance with the present invention.
  • the TCS 100 includes a prescriber interface 101, a pharmaceutical interface 102, a pharmacy interface 103 and a management server 104, that communicate via communication mediums 113, such as an electronic prescribing switch 114, and the Internet 115.
  • communication mediums 113 such as an electronic prescribing switch 114
  • the Internet 115 such as an electronic prescribing switch 114
  • users access the system through one of the interfaces to append information sets to the transnomic code
  • the management server 104 automatically adds information to the transnomic code, or both a user and the management server 104 may add information to the transnomic code.
  • the prescribing interface 101 may be implemented using any type of computing device for operating a web browser 106.
  • the computing device is defined as a device that enables a user to browse a remote web site through the communication medium using, for example, a web browser. Examples of the computing device include a desktop computer, a lap top computer, a personal digital assistant, an interactive wireless communications device, a handheld computer, a computer server, smart phones, tablets, mobile computing devices or the like, which connects with the communication medium. Additionally, the computing device may include any number of known peripheral devices that cooperate with the computing device, such as a printer, a scanner, a bar code scanner, facsimile machine and the like.
  • the prescriber interface 101 may be accessed from anywhere, and in particular embodiments are accessed where prescriptions are prescribed, such as a medical private practice, a hospital, or a clinic.
  • the prescriber may still be located anywhere a mobile device can access the TCS 100 on a wireless network, such as but not limited to, WiFi, 3G, or 4G network where they can initiate a prescription.
  • the prescriber interface 101 enables a prescribing entity, such as a physician, to access the management server 104 to prescribe a medication to a patient via an electronic prescription switch and to append data to the transnomic code.
  • the transnomic code is paired with the electronic prescription when completed in the prescriber interface 101 and sent into the communication mediums 113.
  • the paired data may then be split into two transmissions at the management server 104, with the electronic prescription being submitted to the electronic prescription switch (denoted as eRx switch) 114 for ultimate delivery to the chosen pharmacy.
  • a switch refers to an organization that receives live pharmacy claims from a pharmacy management system and then routes them to the appropriate claims processor for pharmacy benefit manager ("PBM") functions. Once the claims processor adjudicates the claim and sends a response, the switch also returns the adjudicated claim from the claims processor to the management server 104 from where it originated.
  • the transnomic code is updated with the new information received at the management server 104 during this step and is then stored to be made available to other users with appropriate access.
  • the pharmaceutical interface 102 is implemented using one or more computing devices for operating a web browser 107.
  • the pharmaceutical interface 102 may be accessed from anywhere and particularly at a company's physical facilities. It is also contemplated that the pharmaceutical interface 102 may be accessed from a computing device that comprises a main server located at a pharmaceutical company's facilities, which may be remotely accessed by other computer devices.
  • pharmaceutical sales representatives may access the pharmaceutical company's server via a wireless personal digital assistant device, which advantageously enables the sales representatives to access the management server 104 remotely.
  • the wireless personal digital assistant device may be capable of accessing the management server 104 directly without having to first access the pharmaceutical company's server.
  • the pharmaceutical interface 102 contains within it various levels of permission to assign drugs, patient terms, and physicians to transnomic codes.
  • an appropriate party at the pharmaceutical company has protected administrative entry screens to control the drug chosen for available transnomic codes.
  • the party also controls the patient terms (e.g. free, discounts off cash price, reduction of copay, or patient contribution, number of refills, etc.) and establishes parameters for the transnomic code distribution for a specific coupon or marketing discount or sampling program.
  • the pharmacy interface 103 is also implemented using one or more computing devices for operating a web browser 108.
  • the pharmacy interface 103 may be accessed from anywhere, and particularly at a location that dispenses prescriptions and sample prescriptions.
  • the pharmacy interface 103 is capable of accessing the
  • the pharmacy interface 103 may also be used to append data to the transnomic code in the management server 104 and access the stored data for that transnomic code.
  • the pharmacy interface 103 may also contain an application to receive electronic prescriptions from the electronic prescription switch 114 in addition to the tools to access the management server 104.
  • the management server 104 provides functionality for managing transnomic codes utilized in the TCS 100.
  • the management server 104 is operated by a business entity that handles various prescription order processing tasks, collections, distribution of information and customer service tasks associated with the TCS 100.
  • the management server 104 may include software 109 that implements an online registration process (not shown) for enabling other entities, such as physicians, physician practice groups, hospitals, clinics, pharmaceutical companies, pharmacies, and so forth, to register as members.
  • the management server 104 contains administrative interface screens which allow various users with the appropriate privileges to establish terms to allow users to append data to the transnomic codes, as referenced above under Section 2, 'Pharmaceutical interface 102.' The management server 104 may identify customers using any appropriate method, such as cookie retrieval or log-in procedures. Additionally, communications between devices of the TCS 100 preferably use an authenticated certificate in accordance with governmental regulations, such as U.S. Drug Enforcement Administration ("DEA”) policies.
  • DEA Drug Enforcement Administration
  • the management server 104 illustrated in Figure 1 includes components that may be used to implement the above-described features.
  • the exemplary management server 104 includes a web server 110, which accesses a database collection 111 that includes a database of sample prescription information 112 and related content.
  • the web server 110 also manages a web site accessible via the communication medium 113.
  • the web server 110 may also process requests made with an appropriate permission level or de-coding key for the prescription information contained in the transnomic code, review and authenticate the prescription information, and send and receive prescription information to and from the prescriber interface 101, the pharmaceutical interface 102 and the pharmacy interface 103 via the communication medium 113.
  • the information may be used to provide prescriptions to patients via submission to the electronic prescribing switch 114, track the prescriptions through to the endpoint of patient pick-up at the pharmacy and generate prescription marketing reports among other functions.
  • the web server 110 communicates with management server software 109 as well as the database collection 112 to manage the prescription process and to provide prescription related information to appropriate users. Additionally, the management server software 109 generally implements the functions of the management server 104, including releasing information, populating the database 111 and operating the management server web site. a. Database Collection 1 11
  • the database collection 111 illustrated in Figure 1 includes the database 112 for storing transnomic code related information.
  • the database 112 contains a plurality of files, each designated by a unique encrypted transnomic code corresponding to a particular medication.
  • each medication produced by a pharmaceutical company that uses the TCS 100 has a corresponding transnomic code in the database 112, wherein the transnomic code for each medication may be directed at particular lots of medication, particular prepackaged medications, and the like.
  • the transnomic code may be randomly generated or may be generated using a convention where the transnomic code has specific meaning. Specifically, in the latter instance, a person with knowledge on how to read the transnomic code may obtain information about the corresponding medication by analyzing the transnomic code.
  • the transnomic code 10 may have a tracking code 15 that comprises static information with at least one read header 22 and extensible content 24, wherein the read header 22 provides instructions relating to the extensible content 24 that identifies other information that is dynamically added over the product life-cycle as well as additional information deriving from effects after the use of the product.
  • the transnomic code 10 is a type of "living-code" that is both the extensible and dynamic embodiment of the information contained within the transnomic code through time as more information is added to it, reflecting various events in the product life-cycle as well as adding information deriving from effects after the use of the product.
  • This is the key distinction from many other industry standard methods of describing codes, such as, but not limited to, bar-codes or product labels, in which a fixed or static set of fields, or a fixed/static format is utilized.
  • the transnomic code 10 is infinitely flexible over the product life-cycle and pattern of use. This flexibility of the transnomic code 10 is reflected in that according to embodiments, at various times, the management server may be accessed by different parties through particular interfaces to both retrieve and add information in real time and date to the transnomic code 10 electronically.
  • each information set 20, 30, 40 and so on added by an interface of the TCS 100 to the transnomic code 10 has two parts, a read header 22, 32, 42 respectively, as well as extensible content 24, 34, 44.
  • the read header 22, 32, 42 is information that is relevant to the interpretation, or security, of the information and extensible content 24, 34, 44 forms the rest of the transnomic code 10.
  • Each information set 20, 30, 40 is associated to a particular transnomic code 10 by use of and reference to the tracking code 15. So, for example, a transnomic code 10 may be utilized by the TCS 100, wherein the transnomic code 10 corresponds to a health care product used by a consumer, such as a pharmaceutical product.
  • the pharmaceutical product and consumer information is governed by HIPAA and accordingly, to the transnomic code 10 also contains sensitive information governed by HIPAA privacy rules and contains Protected Health Information ("PHI”) with respect to who has what level of access to clinical outcomes information on the use of that pharmaceutical product.
  • HIPAA privacy rules and contains Protected Health Information ("PHI") with respect to who has what level of access to clinical outcomes information on the use of that pharmaceutical product.
  • PHI Protected Health Information
  • the transnomic code 10 with a tracking code 15 may include a first information set 20 having a read header 22 and extensible content 24.
  • the read header 22 may contain specific code instructions regarding how the information in extensible content 24 is to be accessed, unpacked, read and interpreted, and further may govern access to subsets of information in the extensible content 24 to users based upon user access privileges to a particular set or subset of information.
  • the extensible content 24 may include information regarding the pharmaceutical associated with the transnomic code 10, the type and dosage of the pharmaceutical, pharmaceutical company that manufactured the medication, the location of manufacture, the lot number, NDC, other industry standard nomenclature related to a pharmaceutical product, and the like.
  • the transnomic code 10 may then have added to it another information set 30 having a read header 32 and extensible content 34.
  • the read header 32 may contain specific code instructions regarding how the information in extensible content 34 is to be accessed, unpacked, read and interpreted, and further may govern access to subsets of information in the extensible content 34 to users based upon user access privileges to a particular set or subset of information.
  • the extensible content 34 may include prescription information, the condition or diagnostic code of the patient that is receiving the prescription and the like.
  • the transnomic code 10 may further have third information set 40 having a read header 42 and extensible content 44 added to the transnomic code 10.
  • the read header 42 may contain specific code instructions regarding how the information in extensible content 44 is to be accessed, unpacked, read and interpreted, and further may govern access to subsets of information in the extensible content 44 to users based upon user access privileges to a particular set or subset of information.
  • the extensible content 44 of the information set 40 may include health outcomes information with a read header 42 that defines the ability of any other user through the TCS 100 to access the extensible content 44 in that transnomic code 10 based on permissions according to HIPAA privacy rules.
  • Each of the information sets 20, 30 and 40 are combined to form an embodiment of the transnomic code 10.
  • the read header 22, 32, 42 of each information set 20, 30, 40 may also include a time stamp, which permits the information sets 20, 30, 40 to be added asynchronously to the transnomic code 10.
  • the various interfaces associated TCS 100 with the various access and user points may have different latencies with respect to how they will add/update information, but because of the time stamp it does not matter what order the header/information sections are added, the transnomic code 10 can at any time be read and unpacked, and the contained information placed in its appropriate time series sequence as needed.
  • the read header 22 may contain specific code instructions to the management server regarding how the information in extensible content 24 is to be accessed, unpacked, read and interpreted.
  • the read header 22 may also allow access to subsets of information to users based upon user access privileges to a particular set or subset of information.
  • the TCS 100 may grant access to the entire set of information contained within the transnomic code 10, or may only allow certain users access to information going forward in time from their access point along the chain of information that was built over the life-cycle of the product. On the other hand, some users may only be allowed access to retrospective analysis of information from a certain historical point in the code's development.
  • the "read header” is particularly useful because it allows various users through defined interfaces to access the management server to append information to the transnomic code, with the information in a read header on how to read the content of the extensible content added within the transnomic code, so that other users may have access to that content directly, without needing separate updating and communication between users.
  • This is not only important across different types of users reflecting different interests and needs in the particular transnomic code at a point in time, but also creates robustness in the ability of the users through the management server to interpret the extensible content through time. Given that some product life-cycles may last for many years or decades (such as implantable devices in orthopedics or cardiac and diabetic implant devices), this can be quite important.
  • the extensible content is populated by inputting information into the TCS 100 by the various interfaces, such as prescriber interface 101, the pharmaceutical interface 102, the pharmacy interface 103, and/or from another source or interface, such as a pharmacy benefit manager or electronic prescription switch, that has the desired information.
  • the information may be inputted in any number of ways known by those skilled in the art, such as automatic uploading when a triggering event occurs during the life-cycle of the product or manual inputting of the information.
  • the database collection 111 there may be several processes (not shown) such as ID generators, number generators and temporary storage units that may work with the database collection.
  • the database collection 111 may be implemented using a variety of different databases such as relational databases, flat file databases, or object oriented databases.
  • the database collection depicted in Figure 1 is comprised of one database 112, it is recognized that in other embodiments, the database collection may include other databases.
  • the database collection may be implemented as a single database with separate tables or as other data structures that are well known in the art such as linked lists, stacks, binary trees, and so forth.
  • the communication mediums 113 include an electronic prescription switch 114 and the Internet 115, though a wide range of interactive communication mediums may be employed in the TCS 100 as is well known to those skilled in the art via encrypted, HIPAA compliant encoding.
  • Figure 1 illustrates an embodiment wherein the management server 104 primarily implements the TCS process
  • the management server 104 may include or work in conjunction with one or more third parties (not shown) to provide the transnomic code service.
  • the third party web site may receive requests for prescriptions, samples and/or send prescriptions or sample prescriptions to the pharmacies.
  • a pharmacy benefit manager may be central to communicating data between the management server and the users that interact with the transnomic code along the chain to a patient receiving a pharmaceutical.
  • a prescriber may access and request electronic e-sampling coupons and attach them electronically to their prescription, forming another example of the dynamic nature and options that prescribers would have in using the Transnomic Coding System.
  • the transnomic coding system allow for the addition of various types of information that may be pertinent in the tracking of goods and particularly in tracking pharmaceuticals along the chain of custody of the those goods. It further allows the tracking association of information regarding the goods to be accessed by individuals to provide them with metrics or measurements by which to make determinations regarding results of the use of the goods, such as the effectiveness of a pharmaceutical for a particular patient, a particular illness, condition or the like.
  • TCS 100 is described using "a" management server 104, it is recognized that the management server 104 may comprise multiple different sites.
  • a pharmaceutical company via the pharmaceutical interface 102, assigns a transnomic code to a product and stores the same in the management server 104.
  • the management server 104 assigns a transnomic code to a product and stores the same in the management server 104.
  • the pharmaceutical company uses the pharmaceutical interface 102 via web browser 107 to accesses the web site of the management server 104.
  • the web site Once logged into the web site, the web site provides an option for the pharmaceutical company to assign a transnomic code to a product. Additionally, the web site prompts the pharmaceutical company to submit information about the product that will be used in conjunction with the transnomic codes. This information may include the lot number, the corresponding medication type, the terms available for the patient, and any other pertinent information as determined by the industry (e.g., NDC number) to establish a base for a transnomic code for the product.
  • the management server 104 stores a number of transnomic codes
  • each transnomic code corresponds to one product that the pharmaceutical company plans to distribute comprising and matching with a single prescription. Furthermore, information obtained during the step 200 is populated into the corresponding transnomic code to build the extensible transnomic code.
  • the management server 104 provides the transnomic codes to the requesting pharmaceutical company.
  • the transnomic codes are provided to the pharmaceutical company, wherein the management server 104 may be accessed by a pharmaceutical company through a pharmaceutical interface 102. The pharmaceutical company then has the ability to associate the transnomic codes to particular products.
  • the pharmaceutical interface 102 may be capable of downloading the list of transnomic codes or otherwise accessing the list of transnomic codes via the management server web site.
  • the pharmaceutical company activates the transnomic codes and the codes follow the product through the entire chain of custody.
  • the transnomic code is a "living code” that is both an extensible and a dynamic embodiment of the information contained within the code through time as more information is added to it, reflecting various events in the product life-cycle as well as adding information deriving from effects after the use of the product.
  • the transnomic code as described previously is created through the TCS 100 at the request of the pharmaceutical company, and the codes are stored on the management server 104. As information is added, the transnomic code stored on the management server 104 is updated and stored on the management server 104.
  • transnomic codes stored on the management server 104 and add information to the transnomic code, in order to further build the code and accurately reflect the life of the product from manufacture to dispensing.
  • This is the key distinction from many other industry standard methods of describing codes, such as, but not limited to, bar-codes or product labels, in which a fixed set of fields, or a fixed format, of descriptor is defined, and the fields are filled by information as available.
  • the transnomic code is indefinitely flexible over the product life-cycle and pattern of use.
  • the management server is accessed by different parties through corresponding interfaces, wherein the parties can both retrieve and add information to the transnomic code electronically.
  • a step 204 medications are prescribed to a patient.
  • a patient visits a physician whom was previously allocated sample codes as discussed above.
  • the patient-physician examination may be performed via a real time video conferenced telemedicine appointment.
  • the physician/prescriber examines the patient and determines that the patient should take a particular medication.
  • the physician may then access the management server 104 through the prescriber interface 101 and prescribe a pharmaceutical product.
  • the physician can prescribe the prescription.
  • the physician accesses the management server 104 web site, app, or third party e-prescribing entity if the prescriber interface 101 includes access to both.
  • the physician then navigates to an application of the web site that enables the physician to "e-prescribe" the prescription.
  • "e-prescribe” means that the physician can use a computer device to transmit the prescription to a medication dispensing facility, such as a pharmacy.
  • the "e-prescribe" application prompts the physician for information required to fill the prescription.
  • This information may include the desired dispensing location (e.g. pharmacy location), patient information (e.g. name, age, sex, and other identifiers) and sample code, if any.
  • the physician then submits the prescription, and the information is routed to the management server 104.
  • the management server 104 may then perform any number of processes, including adding content to the transnomic code in the database 112 and checking the database collection 111 to determine whether or not the patient was recently prescribed similar medication that may indicate unlawful conduct (e.g.
  • the TCS 100 also may authenticate the prescriber by verifying that the prescriber is lawfully able to prescribe the medication by referencing the prescriber' s DEA or National Provider Identifier (NPI) number designation.
  • NPI National Provider Identifier
  • the prescription is sent to a participating dispensing location.
  • the "e-prescribe" application transmits the prescription from the management server 104 to the pharmacy interface 103 via the communication mediums 113.
  • the communication mediums may, or may not include a combination of the electronic prescription switch 114 and the Internet 115.
  • the prescription may be sent via fax.
  • the prescription is routed to an organization that administers the electronic prescription switch 114.
  • the transmission to the electronic prescription switch 114 may be initiated by an e- prescribing application with direct access to the switch 114 or through the management server via the Internet 115.
  • the pharmacy interface 103 receives the electronic prescription, triggering any number of actions. If the electronic prescribing switch 114 has accessed the appropriate PBM prior to delivery of the sample code and prescription to the pharmacy interface 103, then the pharmacy may dispense the prescription and complete a dispensing confirmation to send to the PBM. If the PBM has not yet been accessed, the pharmacy interface 103 instructs a pharmacy's practice management system, which may or may not be part of the pharmacy interface 103, to send the prescription to the appropriate PBM for adjudication. In general, in the step 208, the TCS 100 preferably coordinates with a pharmacy benefit manager verification that the prescription is valid (e.g.
  • the pharmacy interface 103 receives a copy of the prescription in the form of an encrypted email or faxed sample prescription having a bar code that can be scanned at the pharmacy.
  • the pharmacy interface 103 transmits prescription information to the management server 104 via the PBM.
  • the pharmacy interface 103 may automatically transmit the desired information when the prescription is delivered to the patient as an additional transmission.
  • the pharmacy interface 103 may produce a bar code (e.g., print a bar code label via a printer 117) that is affixed to a package (e.g., container) of the prescription.
  • the bar code corresponds to the transnomic code for the prescribed medication and stored on the management server 104.
  • the pharmacy interface 103 recognizes the bar code and automatically updates the transnomic code on the management server database 112 with additional prescription information, such as the date and time the patent picked up the prescription.
  • the pharmacy employee may enter a prescription
  • identification number that corresponds to the prescription into the pharmacy interface 103. This allows for the collection of data specific to the patient receipt of the
  • prescription, as adjudication through the PBM is often asynchronous to the time of pickup by a patient.
  • a similar process integrating shipment delivery data may be used to support the collection of the data for prescriptions received at home by a patient.
  • the pharmacy interface 103 assist in reporting information about the prescribed medication and the patient by interacting with a designated PBM.
  • the PBM functions to manage eligibility, conduct utilization reviews for appropriateness of a therapy, and perform settlements between pharmacies,
  • the PBM also is a primary conduit for the collection of data that is ultimately added to the transnomic code.
  • step 209 the prescription information collected by the PBM is delivered back to the TCS 100 for addition to the transnomic code stored in the database 112.
  • the PBM or the electronic prescription switch 114 may be used to analyze drug interactions between medications prescribed to patients.
  • the pharmacy interfaces 103 have "keys" that enable the pharmacy interface 103 to read the prescription submitted by the management server 104. If the pharmacy interface 103 does not have the appropriate key, then the pharmacy interface 103 cannot open the sample prescription. Also, the pharmacy interface 103 may be given a unique pharmacy identifier. When the transnomic code is accessed by the pharmacy interface 103, the unique pharmacy identifier is automatically sent to the management server 104. If the pharmacy identifier matches pharmacy information populated in the corresponding transnomic code (step 204), then the management server may send a "key" code to the pharmacy interface 103 that enables the pharmacy interface 103 to open the prescription.
  • a step 210 the pharmaceutical company, having the pharmaceutical interface 102, obtains information from the transnomic code.
  • the pharmaceutical company having the pharmaceutical interface 102, obtains information from the transnomic code.
  • the pharmaceutical company purchases information from the management server 104, which was acquired for the transnomic codes that were allotted to the pharmaceutical company in the step 200.
  • the pharmaceutical company accesses the
  • the pharmaceutical company or authorized third party can download information stored in the database 111 after paying a fee to the management server entity.
  • the pharmaceutical company or other subscribing company is provided with a unique identification number, after paying a fee, which allows them to access the sample code files.
  • the pharmaceutical company has access limited to only non-confidential information (in other words, no PHI).
  • the pharmaceutical company or authorized third party may be denied access to private patient information, such as social security numbers or names, but has access to non-confidential information such as demographic and metric data.
  • the pharmaceutical company has access to valuable marketing information, but yet does not violate a patient's confidentiality/HIPAA rights.
  • a prescriber may also access the transnomic code through a prescriber interface 102.
  • the prescriber may then generate a report through use of a data report application.
  • the report may be delivered by the TCS 100 after the prescriber pays a fee.

Abstract

L'invention concerne un procédé et un système pour suivre des marchandises, le système étant système à code transnomique. Le système à code transnomique comprend une interface de prescripteur, une interface pharmaceutique, une interface de pharmacie et un serveur de gestion qui communique via des supports de communication, tel qu'un commutateur électronique de prescription et Internet. Le code transnomique est un code dynamique qui comprend un code de suivi et un ou plusieurs ensemble(s) d'informations, chaque ensemble d'informations comprenant un en-tête de lecture et un contenu extensible. Le code transnomique est affecté à un produit, tel qu'un produit pharmaceutique. Le système permet d'ajouter des ensembles d'informations au code transnomique à un point quelconque pendant le cycle de vie d'un produit.
PCT/US2013/074179 2012-12-10 2013-12-10 Procédé et système de suivi de marchandises WO2014093377A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/710,167 US9235869B2 (en) 2005-03-11 2012-12-10 Method and system for tracking goods
US13/710,167 2012-12-10

Publications (1)

Publication Number Publication Date
WO2014093377A1 true WO2014093377A1 (fr) 2014-06-19

Family

ID=50934900

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/074179 WO2014093377A1 (fr) 2012-12-10 2013-12-10 Procédé et système de suivi de marchandises

Country Status (1)

Country Link
WO (1) WO2014093377A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080022005A1 (en) * 2006-07-24 2008-01-24 Microsoft Corporation Glitch-Free Media Streaming
US20080208626A1 (en) * 2005-03-11 2008-08-28 Eric Greenman Novel Methods And Systems For Prescribing Sample Prescriptions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080208626A1 (en) * 2005-03-11 2008-08-28 Eric Greenman Novel Methods And Systems For Prescribing Sample Prescriptions
US20080022005A1 (en) * 2006-07-24 2008-01-24 Microsoft Corporation Glitch-Free Media Streaming

Similar Documents

Publication Publication Date Title
CA2618141C (fr) Nouveaux procedes et systemes d'etablissement de prescriptions d'echantillons
US11587179B2 (en) Systems and methods for determining and communicating patient incentive information to a prescriber
EP2767951B1 (fr) Dispositif, procédé et programme de traitement de données
US8060379B1 (en) Systems and methods for alternate pricing for prescription drugs
US10417380B1 (en) Systems and methods for determining and communicating a prescription benefit coverage denial to a prescriber
US10635783B2 (en) Systems and methods for determining patient adherence to a prescribed medication protocol
US20060235726A1 (en) System and method for pharmaceutical item and prescription management
US20200082327A1 (en) Healthcare system for recording and monitoring transactions of system participants
CA2884949C (fr) Systemes et methodes de verification de la correlation de diagnostic et de medication dans le cadre d'un programme qualifiant de verification d'admissibilite
US8392219B1 (en) Systems and methods for streamlined patient enrollment for one or more healthcare programs
US11893534B2 (en) System for inventory management
US20130238360A1 (en) System and method for maintaining and utilizing family medical history
KR20040053269A (ko) 처방조치 시스템 및 방법
US10373255B1 (en) Methods and systems for maintaining pharmacy provider networks
KR102526977B1 (ko) 지능형 전자 처방전 서비스 제공 방법 및 장치
US8543417B1 (en) Systems and methods for dispensing and collecting data related to controlled substances
US9235869B2 (en) Method and system for tracking goods
US20030225627A1 (en) Method for retail distribution of medical products
Kilbridge et al. E-prescribing
WO2014093377A1 (fr) Procédé et système de suivi de marchandises
AU2012216288B2 (en) Novel methods and systems for prescribing sample prescriptions
KR100768139B1 (ko) 통신망을 이용한 전자 처방전 중계 서비스 방법 및 시스템
US20150379207A1 (en) Universal medical access card system and process thereof
US20160048656A1 (en) System for using medication samples to measure medication acquisition and improve patient outcomes
AU2010246368A1 (en) The Delivery of Medical Prescriptions

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13863157

Country of ref document: EP

Kind code of ref document: A1

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13863157

Country of ref document: EP

Kind code of ref document: A1