# US 12,182,082 B2 · Data repositories > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,182,082 B2 - Document ID: US12182082B2 - Status: Granted - Kind: B2 - Application number: 16/630,971 - Filed: 2018-07-12 - Published: 2020-07-16 - Granted: 2024-12-31 - Earliest claimed: 2017-07-18 - Assignees: Koninklijke Philips N.V. - Applicants: Koninklijke Philips N.V. - Inventors: Iwo Willem Oscar Serlie; Josephus Antonius Maria Schipperheijn; Roy Franciscus Petrus Van Pelt - Web page: https://patentgrep.com/patent/US12182082B2 ## CPC - G06F 16/212: {with details for data modelling support} - G16H 30/20: for handling medical images, e.g. DICOM, HL7 or PACS - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract Presented are concepts for provisioning an instance of a data repository. A domain model specification is obtained, the domain model specification comprising: an entity definition defining an entity of a data repository to be provisioned; and an operation definition defining one or more operations to be supported by the data repository to be provisioned. An instance of a data repository is generated based on the entity definition and operation definition of the domain model specification. ## Claims ### Claim 1 An apparatus for provisioning an instance of a clinical data repository, the apparatus comprising: a data acquisition unit configured to obtain a domain model specification, the domain model specification comprising an entity definition defining an entity of a clinical data repository to be provisioned, and an operation definition defining searching parameters of a search operation to be supported by the clinical data repository to be provisioned, wherein the searching parameters relate to a plurality of resources so as to support a composite search query; and a processing unit configured to generate an instance of the clinical data repository based on the entity definition and the operation definition of the domain model specification, wherein the instance of the clinical data repository is configured to normalize clinical data relating to one or more patients according to the searching parameters and the search operation defined by the operation definition such that the instance of the clinical data repository is automatically optimized for real-time specific in-workflow analytics relative to the searching parameters and the search operation; wherein the data acquisition unit comprises: an input interface configured to receive, from a user, an input signal representative of at least one of the entity definition and the operation definition; and a specification unit configured to generate the domain model specification based on the input signal received from the user; wherein the generated instance of the clinical data repository comprises a normalized part that is optimized according to the operation definition and an entity-based part having one or more attributes defined by the entity definition to automatically optimize the search operation, and wherein the generated instance of the clinical data repository further comprises a service interface configured to implement the search operation defined by the operation definition. ### Claim 2 (depends on 1) The apparatus of claim 1, wherein the entity definition comprises a structured description of the entity according to a predetermined specification format. ### Claim 3 (depends on 1) The apparatus of claim 1, wherein the entity definition comprises a definition of an attribute of the entity and permissible values of the attribute. ### Claim 4 (depends on 1) The apparatus of claim 1, wherein the generated instance of the clinical data repository comprises an SQL-server instance of the data repository. ### Claim 5 (depends on 1) The apparatus of claim 1, wherein the generated instance of the clinical data repository comprises entity, junction and version tables, and searchable content and indices. ### Claim 6 (depends on 1) The apparatus of claim 1, wherein the data acquisition unit is further configured to obtain an updated version of the domain specification, and wherein the processing unit is further configured to modify the generated instance of the data repository based on the updated version of the domain model specification. ### Claim 7 (depends on 1) The apparatus of claim 1, further comprising a communication interface configured to communicate with one or more databases so as to obtain at least one of: the entity definition and the operation definition. ### Claim 8 A method for provisioning an instance of a clinical data repository, the method comprising: receiving, from a user, an input signal via an input interface, the input signal being representative of at least one of an entity definition and an operation definition; generating a domain model specification based on the input signal received from the user, the domain model specification comprising an entity definition defining an entity of a clinical data repository to be provisioned, and an operation definition defining a search operation to be supported by the clinical data repository to be provisioned, wherein the search operation defines one or more searching parameters for relating to a plurality of resources so as to support a composite search query; and generating an instance of the clinical data repository based on the entity definition and the operation definition of the domain model specification, wherein the instance of the clinical data repository is configured to normalize clinical data relating to one or more patients according to the searching parameters and the search operation defined by the operation definition such that the instance of the clinical data repository is automatically optimized for real-time specific in-workflow analytics relative to the searching parameters and the search operation; wherein the generated instance of the clinical data repository comprises a normalized part that is optimized according to the operation definition and an entity-based part having one or more attributes defined by the entity definition to automatically optimize the search operation, and wherein the generated instance of the clinical data repository further comprises a service interface configured to implement the search operation defined by the operation definition. ### Claim 9 (depends on 8) The method of claim 8, wherein the entity definition comprises a structured description of the entity according to a predetermined specification format. ### Claim 10 (depends on 8) The method of claim 8, wherein the entity definition comprises a definition of an attribute of the entity and permissible values of the attribute. ### Claim 11 (depends on 8) The method of claim 8, wherein the generated instance of the clinical data repository comprises an SQL-server instance of the data repository. ### Claim 12 (depends on 8) The method of claim 8, wherein the generated instance of the clinical data repository comprises entity, junction and version tables, and searchable content and indices. ### Claim 13 (depends on 8) The method of claim 8, further comprising: obtaining an updated version of the domain model specification, and modifying the generated instance of the clinical data repository based on the updated version of the domain model specification. ### Claim 14 A non-transitory computer readable medium storing instructions for provisioning an instance of a clinical data repository that, when executed by at least one processor, cause the at least one processor to: receive, from a user, an input signal via an input interface, the input signal being representative of at least one of an entity definition and an operation definition; generate a domain model specification based on the input signal received from the user, the domain model specification comprising an entity definition defining an entity of a clinical data repository to be provisioned, and an operation definition defining a search operation to be supported by the clinical data repository to be provisioned, wherein the search operation defines one or more searching parameters for relating to a plurality of resources so as to support a composite search query; and generate an instance of the clinical data repository based on the entity definition and the operation definition of the domain model specification, wherein the instance of the clinical data repository is configured to normalize clinical data relating to one or more patients according to the searching parameters and the search operation defined by the operation definition such that the instance of the clinical data repository is automatically optimized for real-time specific in-workflow analytics relative to the searching parameters and the search operation; wherein the generated instance of the clinical data repository comprises a normalized part that is optimized according to the operation definition and an entity-based part having one or more attributes defined by the entity definition to automatically optimize the search operation, and wherein the generated instance of the clinical data repository further comprises a service interface configured to implement the search operation defined by the operation definition. ### Claim 15 (depends on 14) The non-transitory computer readable medium of claim 14, wherein the generated instance of the data repository data comprises an SQL-server instance of the repository.