EP1787231A2 - Method of identifying data relating to individuals for the purpose of chaining said data - Google Patents
Method of identifying data relating to individuals for the purpose of chaining said dataInfo
- Publication number
- EP1787231A2 EP1787231A2 EP05802746A EP05802746A EP1787231A2 EP 1787231 A2 EP1787231 A2 EP 1787231A2 EP 05802746 A EP05802746 A EP 05802746A EP 05802746 A EP05802746 A EP 05802746A EP 1787231 A2 EP1787231 A2 EP 1787231A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- identifier
- data
- individual
- coded
- local
- Prior art date
- Legal status (The legal status 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 status listed.)
- Withdrawn
Links
Classifications
-
- 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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- 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
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
Definitions
- the invention relates to a method for identifying data relating to individuals for carrying out chaining of these data by means of an information processing system comprising local data collection centers, a central data collection unit, data and means of data transmission between the local centers and the central unit.
- the data relating to individuals, on which chaining must be carried out may be, in particular but not exclusively, medical information.
- the medical centers are equipped with computer systems including databases in which are stored data contained in patient files and which are used with more or less complex software to search, sort, group, rankings, statistics, etc.
- These treatments are usually sufficient for the management of patient records in medical centers and hospitals, but do not meet the needs of some specialized centers such as Genetics Centers where the data to be recorded on an individual must include a component allowing to reconstitute a family dimension, essential for the study of genetic diseases, multifactorial complex diseases and pharmacogenetics.
- an information processing system comprising local data collection centers, each equipped with a server and a local database, a central data collection unit equipped with a server and a data collection system; a central database, and means for transmitting data between the local centers and the central unit, each local center comprising means for creating a first coded identifier of an individual by applying a coding algorithm to data identification of the individual, such as name, first name and date of birth, and identification data of the individual's father and mother, such as their surnames, first names and dates of birth,
- the central unit which comprises means for creating a second coded identifier of the individual by application of an algorithm coding the first coded identifier and to record in the central database the second coded identifier instead of the first coded identifier and a correspondence between the second identifier, the aforementioned first order number of the first identifier and the identifier of the first identifier; local center, and comparing the second identifiers in the central unit to achieve individual and family chaining data.
- the creation of an identifier of an individual from identification data of this individual and identification data of his father and mother allows the realization of a family chaining of data concerning the individual and those concerning his father and mother from a simple comparison of identifiers, as well as an individual chaining of the data relating to an individual, and this in a safe and reliable way by avoiding false chaining.
- the identifiers of the individuals comprise three triplets of variables including a triplet of identification data of the individual, a triplet of identification data of his father, and a triplet of identification data from his mother.
- the most reliable identification data are the family name, the given name and the date of birth (the family name being in this case the birth name as opposed to the name of use or marriage, and the first name being the first name of the individual and not a second or third name or a nickname), as has already been verified by several studies.
- the creation of a first coded identifier in the local data collection center ensures the anonymity of the information stored in the database of this local center
- the creation of a second identifier encoded from the first identifier coded, in the central unit ensures the protection of the information stored in the database of the central unit and their strict anonymity, even with regard to those who know the coding algorithm used for the creation of the first identifier, and also with regard to persons having knowledge of the coding algorithm used for the creation of the second identifier, since this algorithm is applied to the coding of already coded and anonymous data.
- the or each coding algorithm mentioned above is mathematically irreversible.
- the method consists in creating the first and second identifiers of the individual by applying to the aforementioned identification data an encoding algorithm and a coding key that is uniquely determined by function of the data to be coded.
- the first identifiers which have been encoded by means of an encoding algorithm and a first coding key are coded again by means of an encoding algorithm and another coding key, the anonymity of the data stored in the central database is fully and definitively protected.
- the method consists in associating with the first coded identifier transmitted by the local data collection center, a number corresponding to a presentation order of the fields constituting this first identifier and creating the second identifier of the individual by coding the fields of the first identifier in the order determined by the aforementioned number associated with this identifier.
- the second identifier of the individual comprises fields containing coded data corresponding to the already coded data of the first identifier, and an additional field containing the aforementioned number which defines the encoding order of the fields of the first identifier.
- the first identifiers of individuals that are created in a local center are recorded in a database of the local center and are transmitted to the central unit after selection and validation by a person authorized.
- the transmission of information between the local center and the central unit is done using secure means.
- the first coded identifiers which are transmitted to the central unit are recorded in a database of this central unit, then are subject to a selection and a selection validation by an authorized person before being processed. view of the creation of the second coded identifiers.
- the card can be of any type, for example chip, magnetic stripe, barcode, etc.
- the method according to the invention consists in using the first coded identifier of the individual, on the card given to the individual, or to recreate this identifier from the identification data on this card.
- the method according to the invention consists in recreating the first identifier coded the individual and use it for search for data about this individual.
- the method according to the invention consists in sending the first coded identifier of the individual who has been recreated or entered on the card issued to the individual to the central unit with an application generating the second coded identifier within a given time period, verifying that no non-trivial modification of the data has taken place since the access request and, if so, informing the applicant of the availability of the data and requesting it reconnect to the central unit to view the data.
- This procedure allows to respect the French law of March 4, 2002, relative to the patients and the quality of the hospital system and according to which a patient must be able to access data concerning him, not only through his doctor but also directly, after a reflection period of 48 hours between the request for access and the delivery of the information, this delivery can not take place less than 48 hours after a non-trivial modification of said information.
- the method according to the invention is applicable, not only to the processing of medical data relating to individuals, but also to the processing of administrative, tax, or other data relating to individuals, whenever it is useful or necessary to use a family dimension, for example in the field of taxes, insurance, wealth management, etc.
- the invention will be better understood and other characteristics, details and advantages thereof will appear more clearly on reading the description which follows, given by way of example with reference to the appended drawings in which:
- FIG. 1 schematically illustrates the main steps of creating a first and a second identifier coded according to the invention
- FIG. 2 schematically illustrates the main steps of access to a file saved in a local database
- FIG. 3 schematically illustrates the main steps of access to data stored in a central database
- FIG. 4 is a flowchart showing schematically the main steps of the method according to the invention.
- reference numeral 10 denotes a local data collection center, which is connected by information transmission means such as, for example, a telecommunications network, to a central unit 12 also connected by the aforementioned data transmission means to a plurality of other local data collection centers.
- information transmission means such as, for example, a telecommunications network
- Each local center 10 comprises a server 14 to which terminals 16 and a local database 18 are connected.
- the central unit 12 comprises a server 20 to which terminals 22 and a central database 24 are connected.
- a first coded identifier 11 of this individual is created by entering identification data of the individual on a terminal 16 installed at the reception office of that individual. local center 10.
- the identification data of the individual 26 include his name (his birth name and not his name of use or marriage name), his first name (this is first name and not a nickname or a second or third name), and his date of birth, as well as the names, first names and dates of birth of his father and mother.
- the individual 26 will provide a family record of civil status to the person responsible for the seizure on the terminal 16 or any other document indicating with certainty the identity of the individual 26 and those of his father and mother. If the individual does not have this kind of document, he will be asked to come back with the document or send it to him. at the local center 10 for verification of the data that has been entered.
- the data entry on the terminal 16 will be done by a procedure comprising the attribution of a quality level to the data entered, this quality level taking into account, for example, the presentation or the non-presentation of the data. an identity card of the individual, the identity of the person making the data entry, his / her level of competence, etc.
- the entry of the identification data of an individual has been made on the terminal 26, an impression of the data entered so that the individual can verify their accuracy.
- the first coded identifier 11 corresponding to the individual 26 is created and a card including this identifier and possibly the corresponding identification data is given to the individual 26, this card being for example a smart card, a magnetic stripe card, a printed card with data in the clear or in the form of a barcode, etc.
- the first coded identifier 11 is coded as follows: A coding algorithm and, preferably, a first coding key are applied to the three triplets of variables formed by the identification data of the individual and his father and mother .
- the coding algorithm is for example a hashing algorithm such as the SHA (Standard Hash Algorithm) which is mathematically irreversible.
- the three identification data of an individual (his name, first name and date of birth) are minced individually, to maintain a high level of security and also to be able to identify later, during a chaining, any errors of data entry and missing data (eg in case of non-knowledge of the date of birth of the individual).
- a first coding key is associated with this algorithm and is determined according to the data to be encoded so as to be unique for this data.
- this coding key is obtained from a matrix of characters recorded in a file called "key file”.
- the selection in this file of the characters that will constitute the specific key associated with the hashing of the data is made by an algorithm that takes into account the length of the data and the value and positions of the characters constituting the data.
- the key file containing the characters from which the encoding key is made is generated randomly.
- the coding key K1 makes it possible to scramble the coding algorithm to avoid "dictionary attacks", as indicated above.
- the result of the coding corresponds to the concatenation of the results of the coding of the various variables formed by the identification data of the individual, his father and his mother.
- the generation of the coded identifier 11 is performed on the . terminal 16, then a record of the data entered and validated is sent to the local database 18 via the server 14, then, when a request to close the file is generated from the terminal 16, the data that has been transferred to the database 18 are deleted from the terminal 16.
- a person responsible for the local center 10 requests, for example from another terminal 16a, the list of data that have been stored in the local database 18 and which have not been transmitted to the central unit. 12.
- This data is transferred by the server 14 to the terminal 16a of the manager, who selects the data to be transferred to the central unit 12 and validates its selection. Then the server 14 will search the local database
- the 18 data relating to each individual who is to be transferred, and creates a file by individual.
- This file is transferred to the central unit 12 by usual data transmission means, for example by a telecommunication network, the transmission preferably taking place in secure form.
- the data relating to an individual that is transferred to the central unit 12 includes the first coded identifier 11 of the individual, a serial number which is the registration number of these data in the database 18, and a identifier of the local center 10, this identifier can be the identity of the person in charge of the local center.
- the corresponding medical data are of course transferred with these identification data.
- the server 20 of the central unit 12 sends an acknowledgment to the server 14 of the local center 10 and records in the central database 24 the data that have just been received.
- a responsible or authorized person of the central unit 12 requests from the server 20, by means of a terminal 22, a list of the data which have been received recently and which have not yet been processed and receives this list back on the terminal 22.
- the responsible or authorized person selects the data that he wants to process and validates his selection, this validation resulting in the generation of an integer for each individual concerned, this number being between 0 and 999999 and corresponding to the coding order in the central unit of the data fields constituting the first coded identifier 11.
- this identifier When this identifier includes 9 data fields (3 identification data fields of the individual, 3 fields of identification data of his father and 3 fields of identification data of his mother), the number of possible combinations of these 9 fields is equal to 9! or 362880.
- a lookup table is used between each possible combination and a six-character number. Initialization of the correspondence table is performed randomly, which allows to use the entire range of possible numbers (between 0 and 999999) without being limited to numbers between 0 and 362880.
- the list of selected individuals and the corresponding numbers are sent from the terminal 22 to the central database 24 which refers to the terminal 22, for each selected individual, the first coded identifier
- This second identifier 12 is generated from a hashing algorithm which may be the same as that used in the local center 10 and a coding key K2 which is available only on the terminal 22 of the responsible or authorized person mentioned above. , this coding key K2 being generated according to the same principle as the first coding key K1.
- the second coded identifier 12 of the individual comprises 10 data fields, the first 9 fields containing the coded identification data, and the tenth field containing the integer which defines the order of the first 9 fields.
- the second coded identifiers 12 are generated on the terminal 22, they are sent to the server 20 of the central unit with the corresponding first coded identifiers 11.
- the server 20 then overwrites the values of the first identifiers coded 11 by the values of the corresponding second coded identifiers 12.
- the corresponding data is deleted from the terminal 22 of the responsible or authorized person.
- a correspondence table between the sequence number of the first coded identifier 11 (or data registration number in the local database 18), the identification of the local center 10 and the second coded identifier 12 is created to facilitate a possible correspondence with the local center 10 in case of chaining problem.
- Individual chaining consists of grouping data from several different local centers that relate to the same individual. When the same identifier associated with different data is found, it is possible to merge these data, which in principle concern the same individual, but after verifications which will make it possible to detect possible correction errors and to correct them.
- the 9 data fields constituting a coded identifier may not all be used, the choice of these fields depending on the missing data in certain fields and also the quality of the data initially recorded.
- a physician has the opportunity to use the terminal 16 of the home of a local center 10 to access data of his patients which are recorded in the local database 18 of this local center.
- the doctor sends the server 14 patient identification data
- the server 14 looks for a corresponding file in the local database 18 and informs the doctor of the results of the search on the terminal 16 and the doctor returns through the terminal 16 to the server 14 a request to consult the folder, which is then transmitted to it by the server 14.
- An individual 26 may also have access to the medical data concerning him, which have been recorded in the database 24 of the central unit 12. For this purpose, as shown in FIG. 3, he may be accompanied by a doctor 28 who can - even have a family file concerning the individual 26, recorded in the database 24 of the central unit 12 and to which the doctor can have access in a conventional manner.
- the doctor does not have such a record of his patient, he will have to use a terminal 16 of a local center 10 to generate in the aforementioned manner the first coded identifier 11 of the individual 26 and transmit it to the server 20 of the central unit 12 by sending to the responsible or authorized person of this central unit a request for generation of the second coded identifier 12 of the individual 26 within a period of, for example, a maximum of five working days and at least 48 hours, provided that no non-trivial modification of the medical data concerning the individual 26 was recorded after the request for access and that no prohibition on consultation of these data by the individual was previously made by a doctor.
- the request for consultation of the data is transmitted by the server 20 to the terminal 22 of the responsible or authorized person who generates on this terminal the coded identifier 12 of the individual 26 and sends it to the server 20.
- the physician 28 can then use the terminal 16 of the local center 10 to reconnect with the server 20 and access the patient's file contained in the database 24.
- a physician connects to the server 20 of the central unit 12 without being accompanied by his patient, he can access write only data relating to his patient that he himself transmitted to the central unit 12.
- the doctor can access other data relating to his patient, contained in the database 24, but read-only. If the doctor wishes to access any other data relating to his patient and transferred by other local centers, 10 he should ask to consult the individual chaining of the data relating to his patient from his file.
- the first step 30 consists of generating the first coded identifier
- the second step 32 consists in recording in the local database 18 data entered and validated and the first coded identifier 11 of the individual.
- the third step 34 is a request, by the person in charge of the local center 10, of a list of data waiting to be transferred to the central unit 12.
- the next step 36 is the sending of this list by the server 14 on the terminal 16a of the manager.
- the next step 38 consists of a selection by the person in charge of the data to be transferred and a validation of the selection.
- the next step 40 is the creation, by the local server 14, of a file per individual, comprising the first coded identifier 11, a serial number and the identification of the local center 10 or of its manager, and the sending this file to the central unit 12 by a secure connection.
- the next step 42 consists in receiving the file by the server 20 of the central unit 12 and sending an acknowledgment to the local server 14.
- the next step 44 is a request, by the person responsible on his terminal 22, for the list of received data not yet processed.
- the list is sent by the server 20 to the terminal 22 of the responsible person.
- the responsible person selects the data that he wants to process, which causes the generation of an integer for each individual concerned, this number being between 0 and
- the next step 50 is sending a list of selected individuals and associated numbers from the terminal 22 to the database 24 via the server 20.
- the server 20 sends to the terminal 22 the first coded identifier 11 of each selected individual as well as the associated number representing the coding order of the fields of this identifier in the second identifier 12.
- the next step 54 is the generation on the terminal 22 of the second coded identifier 12 from the second coding key K2 and the data fields constituting the first coded identifier 11.
- the next step 56 is the sending of the second coded identifier 12 and the first identifier 11 to the server 20 which then replaces the values of 11 by those of 12 and deletes the corresponding data from the terminal 22 of the responsible person and informs a table correspondence between the order of arrival of 11, the local center 10 which sent 11 and the second coded identifier 12.
- the server 20 of the central unit 12 can automatically proceed to family and individual data chaining from the newly registered identifier 12 in the database. 24.
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Biomedical Technology (AREA)
- General Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Epidemiology (AREA)
- Business, Economics & Management (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Storage Device Security (AREA)
- Collating Specific Patterns (AREA)
- Measurement Of The Respiration, Hearing Ability, Form, And Blood Characteristics Of Living Organisms (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0409584A FR2875033B1 (en) | 2004-09-09 | 2004-09-09 | METHOD OF IDENTIFYING DATA RELATING TO INDIVIDUALS FOR THE REALIZATION OF CHAINING THESE DATA |
PCT/FR2005/002252 WO2006030122A2 (en) | 2004-09-09 | 2005-09-09 | Method of identifying data relating to individuals for the purpose of chaining said data |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1787231A2 true EP1787231A2 (en) | 2007-05-23 |
Family
ID=34950564
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05802746A Withdrawn EP1787231A2 (en) | 2004-09-09 | 2005-09-09 | Method of identifying data relating to individuals for the purpose of chaining said data |
Country Status (4)
Country | Link |
---|---|
US (1) | US8229764B2 (en) |
EP (1) | EP1787231A2 (en) |
FR (1) | FR2875033B1 (en) |
WO (1) | WO2006030122A2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050131735A1 (en) * | 2003-12-15 | 2005-06-16 | Degeorge Michael P. | Computerized system and method for identifying and storing time zone information in a healthcare environment |
US8917165B2 (en) * | 2007-03-08 | 2014-12-23 | The Mitre Corporation | RFID tag detection and re-personalization |
US10755812B1 (en) * | 2015-07-31 | 2020-08-25 | Iqvia Inc. | System and method for timely notification of treatment |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4852165A (en) * | 1987-06-12 | 1989-07-25 | National Computer Print, Inc. | Secure system and method for providing personal identifier |
AU5869194A (en) * | 1992-12-03 | 1994-06-22 | Frank E. Frost | System of unique number assignment and genealogical data retrieval |
DE4402903A1 (en) * | 1994-02-02 | 1995-08-03 | Deutsche Telekom Mobil | Method for packet-wise data transmission in a mobile radio network |
WO2001009701A1 (en) * | 1999-08-03 | 2001-02-08 | Amr Mohsen | Network-based information management system for the creation, production, fulfillment, and delivery of prescription medications and other complex products and services |
US6449621B1 (en) * | 1999-11-03 | 2002-09-10 | Ford Global Technologies, Inc. | Privacy data escrow system and method |
AU7182701A (en) * | 2000-07-06 | 2002-01-21 | David Paul Felsher | Information record infrastructure, system and method |
US20020033415A1 (en) * | 2000-09-19 | 2002-03-21 | Cummins Pamela Robin | Secondary security measure for transaction cards |
US20020042879A1 (en) * | 2000-10-10 | 2002-04-11 | Gould Terry A. | Electronic signature system |
CA2461214A1 (en) * | 2001-10-18 | 2003-04-24 | Yeong Kuang Oon | System and method of improved recording of medical transactions |
US20040044730A1 (en) * | 2002-09-03 | 2004-03-04 | Holger Gockel | Dynamic access of data |
-
2004
- 2004-09-09 FR FR0409584A patent/FR2875033B1/en not_active Expired - Fee Related
-
2005
- 2005-09-09 EP EP05802746A patent/EP1787231A2/en not_active Withdrawn
- 2005-09-09 WO PCT/FR2005/002252 patent/WO2006030122A2/en active Application Filing
-
2007
- 2007-03-07 US US11/683,003 patent/US8229764B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
QUANTIN C. ET AL: "Automatic Record Hash Coding and Linkage for Epidemiological Follow-up Data Confidentiality.", METHODS OF INFORMATION IN MEDICINE, vol. 38, 1 January 1998 (1998-01-01), pages 271 - 277, XP009143243 |
Also Published As
Publication number | Publication date |
---|---|
US20070204066A1 (en) | 2007-08-30 |
WO2006030122A3 (en) | 2006-05-04 |
FR2875033A1 (en) | 2006-03-10 |
WO2006030122A2 (en) | 2006-03-23 |
US8229764B2 (en) | 2012-07-24 |
FR2875033B1 (en) | 2015-12-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11637802B2 (en) | Private data sharing system | |
CN103563325B (en) | Systems and methods for securing data | |
CN1833398B (en) | Secure data parser method and system | |
CN103636160B (en) | secure file sharing method and system | |
CN103270516B (en) | System and method for securing virtual machine computing environments | |
CN103178965B (en) | Multifactor or key formula is used to disperse the system and method that data are protected | |
US6845448B1 (en) | Online repository for personal information | |
CN106452737A (en) | Systems and methods for secure multi-tenant data storage | |
CN103959302A (en) | Systems and methods for secure distributed storage | |
CN101689230A (en) | Improved tape backup method | |
CN103229165A (en) | Systems and methods for secure remote storage | |
CN106411909A (en) | Systems and methods for securing data in motion | |
WO2010031926A1 (en) | Method for accessing nominative data such as a customised medical file from a local generation agent | |
FR2953614A1 (en) | SYSTEM AND METHOD FOR PROVIDING SINGLE SOCIAL NETWORK SERVICE ON AN OFFLINE BASIS | |
EP3449410B1 (en) | Biometric authentication system based on vein patterns and unique and unadulterable codings of tree structures and associated method | |
EP1787231A2 (en) | Method of identifying data relating to individuals for the purpose of chaining said data | |
FR3073643A1 (en) | METHOD FOR OBTAINING A DIGITAL IDENTITY OF HIGH LEVEL OF SECURITY | |
WO2005111906A2 (en) | System for automatically generating a medical data message | |
EP3709274B1 (en) | System for electronic voting on the internet | |
EP3190530A1 (en) | Dual medical card for administrative management and medical record and associated methods | |
EP4241190A1 (en) | Authentication method secured by structural decoupling of personal and service identifiers | |
WO2021156078A1 (en) | Method and device for evaluating the correspondence of structured data sets protected by encryption | |
CN118113695A (en) | Method for realizing medical data index in block chain | |
WO2018134505A1 (en) | System for assistance with recovery of lost or stolen objects, allowing objects to be geolocated by means of computer units held by contributing individuals | |
CN103190129B (en) | To moving medial according to the system and method protected |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20070308 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
DAX | Request for extension of the european patent (deleted) | ||
TPAC | Observations filed by third parties |
Free format text: ORIGINAL CODE: EPIDOSNTIPA |
|
17Q | First examination report despatched |
Effective date: 20110701 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: COHEN, OLIVIER |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: COHEN, OLIVIER |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20170401 |