WO2013072524A1 - Zentrale steuerung verteilter organisationsstrukturen - Google Patents
Zentrale steuerung verteilter organisationsstrukturen Download PDFInfo
- Publication number
- WO2013072524A1 WO2013072524A1 PCT/EP2012/072991 EP2012072991W WO2013072524A1 WO 2013072524 A1 WO2013072524 A1 WO 2013072524A1 EP 2012072991 W EP2012072991 W EP 2012072991W WO 2013072524 A1 WO2013072524 A1 WO 2013072524A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- request
- user
- cord blood
- clinic
- database systems
- Prior art date
Links
- 210000004700 fetal blood Anatomy 0.000 claims abstract description 179
- 230000008520 organization Effects 0.000 claims abstract description 45
- 239000002131 composite material Substances 0.000 claims description 21
- 150000001875 compounds Chemical class 0.000 claims description 6
- 210000004369 blood Anatomy 0.000 claims description 5
- 239000008280 blood Substances 0.000 claims description 5
- 210000000130 stem cell Anatomy 0.000 claims description 4
- 210000000056 organ Anatomy 0.000 claims description 2
- 230000000737 periodic effect Effects 0.000 claims 1
- 238000000034 method Methods 0.000 description 49
- 230000008569 process Effects 0.000 description 44
- 238000012545 processing Methods 0.000 description 32
- 238000010200 validation analysis Methods 0.000 description 24
- 230000004048 modification Effects 0.000 description 14
- 238000012986 modification Methods 0.000 description 14
- 238000012790 confirmation Methods 0.000 description 13
- 238000013461 design Methods 0.000 description 12
- 230000001419 dependent effect Effects 0.000 description 10
- 102100036241 HLA class II histocompatibility antigen, DQ beta 1 chain Human genes 0.000 description 9
- 108010065026 HLA-DQB1 antigen Proteins 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 102100028976 HLA class I histocompatibility antigen, B alpha chain Human genes 0.000 description 8
- 102100028971 HLA class I histocompatibility antigen, C alpha chain Human genes 0.000 description 8
- 108010058607 HLA-B Antigens Proteins 0.000 description 8
- 108010052199 HLA-C Antigens Proteins 0.000 description 8
- 239000000523 sample Substances 0.000 description 8
- 102100028972 HLA class I histocompatibility antigen, A alpha chain Human genes 0.000 description 7
- 108010075704 HLA-A Antigens Proteins 0.000 description 7
- 238000003556 assay Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 6
- 239000003814 drug Substances 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 210000003954 umbilical cord Anatomy 0.000 description 5
- 102100040485 HLA class II histocompatibility antigen, DRB1 beta chain Human genes 0.000 description 4
- 108010039343 HLA-DRB1 Chains Proteins 0.000 description 4
- 108010048896 HLA-D Antigens Proteins 0.000 description 3
- 102000009485 HLA-D Antigens Human genes 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 3
- 229940079593 drug Drugs 0.000 description 3
- 230000008676 import Effects 0.000 description 3
- 238000002360 preparation method Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 210000002960 bfu-e Anatomy 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 210000003643 myeloid progenitor cell Anatomy 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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/20—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 management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
Definitions
- the invention relates to a distributed organization structure control system comprising one or more organizations having one or more organizational units, wherein users are assigned to at least one organization and wherein roles are assigned to the users, the roles determining available functionalities within the organization assigned to the user. Moreover, the invention relates to
- control system uses locally available database systems and remote database systems, preferably umbilical cord blood data.
- this is usually about the request for certain drugs or, for example, transplants.
- this is a sales process that is initiated by a search request based on specific criteria.
- a disadvantage of the prior art is that the structure of organizations (for example, a register) is not supported. Thus, only limited possibilities are available.
- the invention was therefore based on the problem that a control system must be provided which addresses the disadvantages of the prior art does not have technology and can support distributed organizational structures, especially with regard to the management of umbilical cord blood data.
- the invention relates to a control system for distributed organizational structures, comprising at least one organization, comprising at least one organizational unit, wherein the organizational unit has technical attributes and wherein the organizational units can be providers and / or interrogators, at least two users, wherein the users at least assigned to an organization, at least one role, wherein the role is assigned to at least one user, and wherein the role determines the available functionalities within the organization assigned to the user, the organization to which a user is assigned determines the view that the user views and wherein a first user can create a search job that is sent to organizations that include provider organizational units, and then the user can make a request to an organization, and one further he user associated with the organization to which the request was made, the request processed.
- An advantage of the invention is that the control system for many different
- control system makes it possible Advantageously, to control a plurality of connected organizational units.
- the organizational unit is selected from the group comprising composite, clinic, facility and / or administration. In doing so, the organizational unit can preferably assume different technical characteristics:
- An association is preferably a combination of at least two clinics, a grouping of at least two institutions or a combination of at least one clinic and at least one institution.
- Cord blood databases An association of one or more clinics and one or more umbilical cord blood bank (s) is also preferred.
- a composite comprises a further composite. Also, there is no provision for clinics to include other clinics or one
- Umbilical cord blood database includes other umbilical cord blood databases. Furthermore, an umbilical cord blood database can not contain a composite.
- An organization corresponds to an organizational unit, for example, if the organizational unit is a stand-alone clinic. In such a case, the clinic is organizational unit and organization at the same time.
- an organizational unit can also contain further organizational units (for example, a group contains a clinic). However, it is not possible for a clinic to contain a compound. Preferably, only one federation can contain further organizational units. It is preferred that a device is selected from the group comprising an umbilical cord blood bank, umbilical cord blood database, a blood bank, a stem cell bank, a donor registry, a tissue bank (also a tissue bank) and / or an organ bank.
- a clinic contains one or more sub-clinics.
- the concrete organizational unit (for example a clinic) is assigned to users.
- One advantage of the invention is that users can also be assigned to several clinics and / or umbilical cord blood database via the composite. This user is enabled by the invention, a central access of the organization with only one account. It is preferable that a user assigned to a federation has no
- a further advantage of the invention is that the platform and / or the system support organization-independent users. That is, it is no longer necessary, as in the prior art, for there to be specific "Search Center Users" and "Provider Users". Thus, the users are allowed to access different organizational units if they are associated with the organization to which these organizational units belong.
- a user is assigned to the organization or organizational units for which he is responsible or active. There may be restrictions such that a user can only be assigned to individual organizational units within a network. The assignment to a compound therefore does not result in the assignment to all the organizational units belonging to the group; this must be done explicitly. As a result, an additional backup is installed, which is advantageous because in the personalized medical field is sometimes very sensitive data in which not every user should automatically get insight.
- the assignment to the back office is also exclusive, which is already ensured by the fact that the back office is a separate organizational unit, which is preferably combined with no other organizational units.
- the user receives an account with which he has access to the organizations or
- a user is assigned to a network, a clinic, a facility or a back-office.
- the user can not simultaneously a composite and independent
- Organizations and organizational units are defined by a role concept. This means that the assignment defines only the access to the corresponding organizational units but not soft data can be specifically accessed and which processing can take place. This is important to enable privacy and to ensure a coordinated flow of inquiries and their response.
- the role is preferably selected from the group comprising administrator, manager, supervisor, coordinator.
- a user is assigned roles that define the available functionality within the user-assigned organizational unit (s).
- the roles here are preferably hierarchical, that is to say a role always contains the authorizations of the role of a lower level.
- Level represents the highest level: 1. Administrator 2. Manager
- the role of the manager has the functionality of accepting acceptance processes.
- the role of the supervisor allows access to all data of the associated
- the role of the coordinator allows access to own data of the assigned organizational units and their reading, writing and / or deleting.
- a higher level always includes the functionalities of the level below.
- the following roles and functions result:
- the clinic administrator has access to - Administration of hospital users
- the access rights of the BackOffice Agent are limited to the Back Office administrator.
- the BackOffice Agent can not provide patient information and
- the role of the clinic manager allows the release of requests or requests requiring approval.
- the clinic supervisor has access to patient data, messages, medical data, search profiles and clinical data for assigned clinics.
- 3.2 Cord blood database supervisor (including all rights of role 4.2)
- the umbilical cord blood database supervisor has access to umbilical cord blood unit (CBU) data, umbilical cord blood database data for associated umbilical cord blood databases
- CBU umbilical cord blood unit
- the role of the Clinic Coordinator allows associated clinics access to their own, in particular self-created patient data and messages to these patients.
- the role of the umbilical cord blood database coordinator allows access to messages for associated umbilical cord blood databases.
- the hierarchical role system eliminates the need to assign any number of roles to a user.
- the roles are dependent on the
- User is assigned to clinic (s) and receives clinic role 3.
- User is assigned umbilical cord blood database (s) and receives one
- the additional user associated with the organization to which the request has been made handle the request, namely accept and display the acceptance to the user who made the request.
- the additional user assigned to the organization to which the request has been made, the request processed and a release step activated.
- control system also applies to others
- Organizations can be applied next to a register. It may be advantageous, for example, that the structure, preferably a method, a system and / or a Device is applied to pharmaceutical companies, government structures, pharmaceuticals, the distribution / management of drugs or treatment methods and / or establishes a link between the doctor, clinic, control instrument and / or authority, for example, to administer and / or appropriate drugs or treatment methods to distribute.
- the invention may be referred to in particular as means for personalized medicine.
- the invention allows the support of networks, for example registers, and thus simplifies previous systems in the field of personalized medicine.
- the platform preferably the umbilical cord blood data platform, supports the creation of networks (for example a registry) of clinics and / or cord blood banks (umbilical cord blood databases) as an organizational unit. This provides new and improved ways to search for data or query inventory.
- networks for example a registry
- cord blood banks umbilical cord blood databases
- independent clinics and stand-alone facilities will support as an organizational unit. That is, it may also continue to give preference clinics or facilities that are not associated with a network. An independent clinic is only those clinics that do not contain sub-clinics. It is particularly preferred that the system and / or the platform continue to be independent umbilical cord blood or umbilical cord blood databases
- An advantage of the invention is the flexibility of the system, which allows it at any time to expand to other organizational units. For example, donor registers or tissue databases may be added as additional facilities and the Scope of the invention thus expand many times. These newly added facilities can also be part of a network.
- the clinics and / or associations with clinics exist as "seekers” or “requestors” and on the other hand, facilities and / or associations with institutions that offer inventories, preparations and / or data. It is quite preferable that an umbilical cord blood database is the device and this
- Umbilical cord blood units (Cordbloodunits) as preparations include or offer.
- the organizational units have technical attributes. There are attributes that all organizational units have. Such attributes include: Name, Description, Address, Contact Person, Billing Address, Contact Person Billing, logo.
- a composite has no further attributes. It is further preferred that a clinic and a facility have an identification (ID) as an additional attribute. In addition, it is preferred that the umbilical cord blood database has not only an identification but also an accreditation.
- the attribute "default language" is no longer an attribute of the organizational units.
- the default language is defined for the specific user. This prevents overlaps when a user is assigned to different organizational units.
- Groups (Group) view (for groups containing clinics and facilities, preferably umbilical cord blood databases) 2. Clinics View (for groupings of clinics or for independent clinics)
- Umbilical cord blood database view (for alliances of umbilical cord blood databases or independent umbilical cord blood databases) 4.
- BackOffice view (for the administration of the system)
- the user is then shown the respective view according to his assignment to organizational units or organizations.
- the available functionalities in a view depend in turn on its user roles.
- a user is assigned to one or more clinics. The user only sees the clinic view.
- a user is associated with one or more umbilical cord blood databases. The user therefore only sees the umbilical cord blood database view.
- a user is one or more clinics and one or more
- the top level menu item is not displayed here. That is, "Groups View” and “Back Office View” are never displayed as menu items. "Clinics View” and “Cord Blood Database View” are displayed only if Clinic (s) and
- Cord blood database exists in a network.
- a component or view is necessary which grants access to the following views:
- Patient Access to "Patient Overview” Contains patient data from an independent clinic or all clinics in the network
- Compound contains only clinics, otherwise it is part of the composite view.
- Umbilical cord blood database of the association of the association.
- CBU Umbilical Cord Blood Units
- Umbilical cord blood database or all umbilical cord blood databases of a network This view is only visible if composite is exclusive
- Cord blood databases and networks are shown.
- the system is navigated to the concrete network and the "Clinics Overview" and “Umbilical Cord Blood Database Overview” are accessed here. There, in turn, the creation of those in the direct context of the network is possible and the assignment is thus implicit.
- the back office is technically also an organizational unit, but it represents a special organizational unit that it has no properties or the like. Creating users for the back office is done via direct access from the back office view.
- the Clinics Overview displays the clinics as well as their data in a tabular context-dependent manner and allows access to the following functions: 1. Presented data
- Umbilical cord blood databases as well as the processing of the umbilical cord blood database associated data. It does not matter if it is an independent one
- Umbilical cord blood database Umbilical cord blood database, umbilical cord blood databases in umbilical cord blood database exclusive or mixed networks.
- the umbilical cord blood database overview always displays the corresponding umbilical cord blood database (s) in tabular form. Only in the case of a BackOffice user, the functionality for creating an umbilical cord blood database for the corresponding group from which one has navigated the umbilical cord blood database overview must be available.
- the representation of the umbilical cord blood databases is also limited by the assignment of the user. This means that the user sees only the umbilical cord blood databases to which he is assigned. A BackOffice user is not subject to these restrictions.
- the users overview is also flexible and according to the navigation path or the organization the users are displayed in a table.
- the Users Overview displays the users and their data in a tabular context-dependent manner and allows access to the following functions:
- the system also includes a Create / Edit User View that provides the following functionality:
- the user is always created and implicitly assigned in the context in which the Create function was called.
- the user In the context of an independent clinic, the user is automatically assigned to this clinic. If you are in the context of a composite, the assignment is made to the composite. The detailed assignment to organizations of the network is as described above. In the context of the back office, the user is assigned to the back office.
- the presentation of the roles has to be adapted, as there are no specific users (SearchCenter User / Cord Blood Database User) anymore.
- the roles are preferably grouped:
- the user to be created / created is a "composite user", ie the user was created in the context of a group (groups), it is possible in the Create / Edit User View to assign to the organizations (Klink (s) and / or (umbilical cord blood databases)).
- a "clinic administrator” or “umbilical cord blood database administrator” which belongs to a network, can advantageously users he creates only
- Umbilical cord blood databases of a group (groups) is a robust behavior for dealing with the assigned roles (for example
- the create and edit group view is opened from the organization overview and enables the display and editing of the fields of the master data of a group (groups).
- the patient overview displays all patient data in a tabular and context-dependent manner.
- All patients of an independent clinic 2.
- Patients of all hospitals of a group In addition, the presentation of patients depends on the assignment of a user to organizational units (clinics) and its role. In principle, a user can only see the patients from the clinics to which they are assigned. In the case of a "clinic coordinator" even only the self-created patients are visible.
- the clinic to which a patient is assigned can be seen in the "Patient Overview" (new column). This is necessary to be able to filter for patients in a clinic.
- the user When the patient is created, the user must be able to select which clinic he wants to assign to the patient according to his assignment to a clinic or to several clinics. Until now the pawls of the search center were always available for selection.
- Umbilical cord blood database or to several umbilical cord blood databases the ability to select which umbilical cord blood database he wants to assign the CBU.
- the assignment in the context of the umbilical cord blood database has always been clear. Now it is advantageously possible to assign these targeted.
- Umbilical cord blood databases are always independent umbilical cord blood database, the umbilical cord blood bank ID can be determined here by the platform. Because the user is assigned to exactly one bank.
- the clinic message overview presents all messages in a tabular and context-dependent manner.
- the presentation of messages depends on the assignment of a user to organizational units (clinics) and its role.
- a user can only see the messages of patients from the clinics to which they are assigned.
- a "clinic coordinator" even only messages from self-created patients are visible.
- a user prefers to only see messages from patients whose data he has access to.
- the umbilical cord blood database Message Overview displays all messages in a tabular and context-dependent manner.
- the umbilical cord blood database to which a message is assigned must be in the
- the BackOffice Message Overview displays all messages in a tabular and context-sensitive manner.
- the Clinic, Cord Blood Database and the Federation (if any) to which a message is associated can be seen in the "Back Office News Overview". This is necessary to be able to filter the messages accordingly. So far, "only" the Search Center and the Cord Blood Database have been listed. There is per request type for each clinic and umbilical cord blood database.
- Request the ability to enable a release step, which takes place after the creation of a "request” and before the transmission to the umbilical cord blood database.
- “Umbilical cord blood database manager” may give a confirmation of a "request”, taking into account the assignment of the user to the corresponding organizational unit, and only if the user is assigned to the corresponding clinic / cord blood database, can he perform the confirmation steps for them Adoption process, the invention introduced the following new "Requests" statuses:
- Umbilical cord blood database visible. On the umbilical cord blood database page, a user must have the role
- the status value "waiting for acceptance” is only visible on the part of the clinic, as the "Request” on the umbilical cord blood database page is not visible until it has the status
- request types It must be configurable per request type if a confirmation step by a user in a "manager role" is necessary or not. This applies to all requesf types available in the platform and / or the system.
- Preferred request types are:
- the clinic administrator can activate confirmation steps at the hospital level (only for assigned clinics). 2.
- the umbilical cord blood database administrator can confirm steps
- Enable cord blood database level (only for assigned umbilical cord blood databases).
- the BackOffice user can confirm steps on clinic as well
- Enable umbilical blood database level The definition for which requesf types require a confirmation step by a user in a manager role must be individually definable / editable per clinic and umbilical cord blood database. According to the invention, no definition of confirmation-relevant Requesf types may be available at the level of a group (groups).
- the status bar represents the new status as follows:
- the detailed "Requesfmatrix” defines the exact status transitions, status buttons (the “reques dialoge”), status texts, confirmation texts and status graphics.
- New or modified "Requests” can be marked On the hospital side, a "request” by a user in the context of a hospital role must then be in principle be marked as changed if the other party makes an adjustment and the user is the owner of the "request”.
- the invention relates to the control system, wherein the user makes a request to an organization for the identification of inventories, wherein the inventories in locally available database systems and in remote
- Database systems are stored, characterized in that 1) locally available database systems and / or local copies of inventories
- Database systems can respond synchronously and / or asynchronously, and
- Results from remote database systems are displayed at specific time intervals.
- the cached results be updated.
- a user can thus make inquiries, which at the same time to all relevant ones
- Database system which are in the organizational units to be sent. Thanks to the new and optimized access authorizations, tailor-made inquiries can be answered quickly and specifically. Furthermore, it is preferred that regularly search queries to remote
- Database systems are placed and the results are stored in the cache. Thus, a user can be informed at regular intervals about the results and also new arrivals.
- the search provides particularly up-to-date results.
- the invention relates to the use of a control system according to the invention for identifying inventories from locally available database systems and remote database systems
- remote database systems are searched and 6) query data is sent to remote database systems, the
- Database systems can respond synchronously and / or asynchronously, and 7) the results are displayed, whereby the user asynchronously receives results from remote database systems at specific time intervals, and
- the use is particularly preferred for the identification of an umbilical cord blood unit. It has been shown that, especially in this field, there is a great need for systems and platforms that support complex organizational structures and allow searches in distributed inventories. The invention therefore simplifies these processes and is advantageous over the prior art.
- the invention thus describes a new technology for the search for stem cell products in distributed inventories. It supports complex decentralized organizational structures, from which the search function advantageously benefits.
- the invention relates to a method for identifying inventories, wherein the inventories are stored in locally available database systems and remote database systems, characterized in that a. locally available database systems and / or local copies of inventories from remote database systems are searched and b. Query data to be sent to remote database systems, the
- Database systems can respond synchronously and / or asynchronously and c. the results are displayed, arriving asynchronously to the user
- Results from remote database systems are displayed at specific time intervals, and d. with the results from remote database systems being cached.
- Cord blood banks allow a particularly efficient handling and fast processing of such questions. This is especially necessary or supplemented by the structural options that have been expanded in the Verbund concept.
- the system or the method supports the search in direct, that is locally available, and distributed, that is, from more distant databases or systems, provided inventories of, for example, stem cell products.
- the system first searches locally available inventories and local copies
- the remote systems can respond synchronously or asynchronously. c) The user will be directly shown the results of the local search together with already arrived results from remote systems. d) The user is informed of asynchronously arriving results from remote systems at adjustable time intervals. e) If search results from remote systems contain products that have already been locally identified in the cache, the search results are updated accordingly and the user is informed. f) Results from remote systems are cached locally to be locally available for later searches. g) The system can periodically make artificial searches on remote systems
- pitching that are used to populate the local cache. This feature is called "pitching".
- Cord blood databases result from the combination of appropriate roles. If, for example, a user is assigned to a clinic and an umbilical cord blood database of a group (groups) and should have access to all patients and messages, etc., the roles “clinic supervisor” and “umbilical cord blood database supervisor” can be assigned to him.
- Figure 1 shows a preferred organizational model. It presents the new technical data structures that support the complex organizational structures of the invention.
- Figure 2 shows the available views using the example of an umbilical cord blood database.
- Figure 3 shows a preferred organization overview. This overview is accessible only to the BackOffice user and displays in tabular form all the organizations created in the platform / system and additionally offers the functionality to create all available organizations and their users as well as related data.
- Figure 4 shows a preferred clinic overview, which is used to display clinics and to process the data assigned to the clinic.
- Figure 5 shows a preferred umbilical cord blood database overflow.
- Figure 6 shows a preferred user overview, which is used to display the users and to edit and create them.
- Figure 7 shows how new users can be created or existing users can be edited.
- FIG 8 gives an overview of the acceptance process (approval process). The figure shows schematically the status transitions.
- Figure 9 shows schematically how the system for the search for distributed inventories is structured.
- Tables 1 to 9 show a detailed list of Reques workflows with all conditions for presentation by the system.
- Verbund A (Clinic + Cord Blood Database Admin) is associated with Federation A and its contained entities.
- Verbund A consists of two clinics and one umbilical cord blood database.
- user A will see the group view. He thus has access to the clinics view, as well as the umbilical cord blood database view and through the administrator roles also access to the user management for the clinics and the umbilical cord blood database.
- Example 2 The following is an example of the user view illustrates:
- Table 2.4 Reservation Request - Workflow / Data
- Table 3.1 Sample Request - Workflow / Data
- Approve activates d d
- HLA-C value HLA-C value
- HLA-DQB1 value HLA-DQB1 value
- HLA-DQB1 Low resolution (see / Medium / Screen design), High / None) Option field Default completely empty
- HLA-A string validation with HLA input field (HLA value) Validator HLA value
- HLA-B string validation with HLA input field (HLA value) Validator
- HLA-C string validation with HLA input field (HLA value) Validator HLA value
- HLA-D B1 String validation with HLA input field (HLA value) Validator
- HLA-DQB1 String validation with HLA input field (HLA value) Validator
- Approve activates d Approved
- HLA-A string validation with HLA input field (HLA value) Validator HLA value
- HLA-C string validation with HLA input field (HLA value) Validator HLA value
- HLA value HLA value
- HLA-DRB1 String validation with HLA input field (HLA value) Validator, X
- HLA-DQB1 String validation with HLA input field (HLA value) Validator, X
- HLA-A string validation with HLA input field (HLA value) Validator HLA value
- HLA-B string validation with HLA input field (HLA value) Validator
- HLA-C string validation with HLA input field (HLA value) Validator HLA value
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Biomedical Technology (AREA)
- Medical Informatics (AREA)
- Game Theory and Decision Science (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Educational Administration (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/359,103 US20140324455A1 (en) | 2011-11-18 | 2012-11-19 | Central control of distributed organizational structures |
AU2012338744A AU2012338744A1 (en) | 2011-11-18 | 2012-11-19 | Central control of distributed organizational structures |
SG11201402403XA SG11201402403XA (en) | 2011-11-18 | 2012-11-19 | Central control of distributed organizational structures |
EP12788202.5A EP2780870A1 (de) | 2011-11-18 | 2012-11-19 | Zentrale steuerung verteilter organisationsstrukturen |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161561398P | 2011-11-18 | 2011-11-18 | |
US61/561,398 | 2011-11-18 | ||
EP11075252 | 2011-11-18 | ||
EP11075253 | 2011-11-18 | ||
EP11075252.4 | 2011-11-18 | ||
EP11075253.2 | 2011-11-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013072524A1 true WO2013072524A1 (de) | 2013-05-23 |
Family
ID=48429018
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2012/072991 WO2013072524A1 (de) | 2011-11-18 | 2012-11-19 | Zentrale steuerung verteilter organisationsstrukturen |
Country Status (6)
Country | Link |
---|---|
US (1) | US20140324455A1 (de) |
EP (1) | EP2780870A1 (de) |
AU (1) | AU2012338744A1 (de) |
DE (1) | DE202012012534U1 (de) |
SG (2) | SG11201402403XA (de) |
WO (1) | WO2013072524A1 (de) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160306503A1 (en) * | 2015-04-16 | 2016-10-20 | Vmware, Inc. | Workflow Guidance Widget with State-Indicating Buttons |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020082866A1 (en) * | 2000-06-27 | 2002-06-27 | Dave Ladouceur | Integrated management of medical information |
US6615317B2 (en) * | 2000-07-07 | 2003-09-02 | Fitech Laboratories, Inc. | Methods and systems for providing a highly scalable synchronous data cache |
EP1851667A4 (de) * | 2005-02-11 | 2011-06-08 | Hipaat Inc | System und verfahren zur privatsphärenverwaltung |
US20060218394A1 (en) * | 2005-03-28 | 2006-09-28 | Yang Dung C | Organizational role-based controlled access management system |
-
2012
- 2012-11-19 US US14/359,103 patent/US20140324455A1/en not_active Abandoned
- 2012-11-19 DE DE202012012534U patent/DE202012012534U1/de not_active Expired - Lifetime
- 2012-11-19 WO PCT/EP2012/072991 patent/WO2013072524A1/de active Application Filing
- 2012-11-19 AU AU2012338744A patent/AU2012338744A1/en not_active Abandoned
- 2012-11-19 SG SG11201402403XA patent/SG11201402403XA/en unknown
- 2012-11-19 EP EP12788202.5A patent/EP2780870A1/de not_active Withdrawn
- 2012-11-19 SG SG10201602914TA patent/SG10201602914TA/en unknown
Non-Patent Citations (1)
Title |
---|
EPO: "Mitteilung des Europäischen Patentamts vom 1. Oktober 2007 über Geschäftsmethoden = Notice from the European Patent Office dated 1 October 2007 concerning business methods = Communiqué de l'Office européen des brevets,en date du 1er octobre 2007, concernant les méthodes dans le domaine des activités", JOURNAL OFFICIEL DE L'OFFICE EUROPEEN DES BREVETS.OFFICIAL JOURNAL OF THE EUROPEAN PATENT OFFICE.AMTSBLATTT DES EUROPAEISCHEN PATENTAMTS, OEB, MUNCHEN, DE, vol. 30, no. 11, 1 November 2007 (2007-11-01), pages 592 - 593, XP007905525, ISSN: 0170-9291 * |
Also Published As
Publication number | Publication date |
---|---|
EP2780870A1 (de) | 2014-09-24 |
SG11201402403XA (en) | 2014-09-26 |
DE202012012534U1 (de) | 2013-05-13 |
AU2012338744A1 (en) | 2014-06-05 |
US20140324455A1 (en) | 2014-10-30 |
SG10201602914TA (en) | 2016-05-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69803657T2 (de) | Wiederverwendbares datenbanksystem | |
DE60025778T2 (de) | Verfahren zum Speichern und Verwalten von Daten | |
DE69903808T2 (de) | Datenverwaltungssystem und verfahren für klinische studien | |
DE102006057149A1 (de) | System und Verfahren zum Erleichtern eines visuellen Vergleichs von Eingangsdaten mit vorhandenen Daten | |
EP1783633B1 (de) | Suchmaschine für eine ortsbezogene Suche | |
DE112016002395T5 (de) | Zugriffskontrolle für Datenressourcen | |
DE202016008173U1 (de) | Einbindung von auswählbaren Anwendungsverknüpfungen in Nachrichtenaustausch-Threads | |
EP0855062A2 (de) | Informationssystem und verfahren zur speicherung von daten in einem informationssystem | |
DE10253676B4 (de) | Verfahren und Vorrichtung für die Fernübertragung sensibler Daten | |
EP1758051A1 (de) | System, Verfahren und Computerprogrammprodukt zur arbeitsflussbasierten Datenverarbeitung | |
EP1611538A2 (de) | Verfahren und anordnung zur automatischen aufbereitung und auswertung medizinischer daten | |
DE112017000695T5 (de) | Arbeitsablauf-Erstellung anhand natürlicher Sprache | |
Watchman | Practitioner‐raised issues and end‐of‐life care for adults with Down syndrome and dementia | |
DE102018132623A1 (de) | System und Verfahren zur Informationsübermittlung von Gesundheitsinformationen | |
EP2780870A1 (de) | Zentrale steuerung verteilter organisationsstrukturen | |
DE202011107588U1 (de) | System zum Erstellen und/oder Führen einer persönlichen Medikationsakte mithilfe eines Computersystems | |
EP3776257B1 (de) | Objektdatenbank zur geschäftsmodellierung mit verbesserter datensicherheit | |
Whitford | The hierarchical consequences of reinvention: evidence from the American bureaucracy | |
DE602004001762T2 (de) | Verfahren und computersystem zur datenzuweisung | |
EP1285315B1 (de) | Informationsverarbeitungssystem und verfahren zu dessen betrieb | |
DE60100846T2 (de) | Verfahren und system zur verwaltung und benutzung von artikeldateien in einem informationsraum, insbesondere medizinische information, und verwendung in informationssystemen | |
Walgenbach | Können wir uns dazu entscheiden, etwas zu glauben? | |
Schaal et al. | Deconstructing “The Truth about Post-Truth”. The contingencies of algorithm-based text analyses | |
Hand | Süchte,«Verhaltenssüchte» und die neue «Sucht-Sucht» | |
WO2024067920A1 (de) | Datenbank eines rechners |
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: 12788202 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2012788202 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012788202 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14359103 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2012338744 Country of ref document: AU Date of ref document: 20121119 Kind code of ref document: A |