Personalized medicine and therapies platform

1. A system for automating client-specific software application configuration management for an enterprise software platform, the system comprising:

at least one data store associated with an enterprise software platform, the data store resident on one or more computers;

at least one processor coupled to the at least one data store; and

a non-transitory memory including processor executable code, wherein the processor executable code upon execution by the at least one processor causes the at least one processor to build a data configuration service for the enterprise software platform, by:

receiving data comprising one or more configuration source files associated with a software application of the enterprise software platform executable on a client computer,

where the one or more configuration source files includes instructions for a set of configuration changes to a version of the software application executable on the client computer; and

processing the received instructions for the set of configuration changes, using: (i) a set of schemas describing at least one of an organization criteria or a validation criteria associated with data structures of the at least one data store and (ii) a set of parameters describing rules governing how to interface with the data structures, to generate an artifact customized for the client computer,

wherein the artifact customized for the client computer comprises a bundle of configuration files configured in a grouped file structure, and

wherein the artifact customized for the client computer is capable of transforming only the version of the software application executable on the client computer in accordance with the instructed set of configuration changes without introducing a change in a master version of the software application of the enterprise software platform executable on one or more other computers,

wherein the processing the received instructions for the set of configuration changes comprises:

initiating a build process to produce a bundled configuration data set based on the one or more configuration source files;

receiving or generating a canonical model of a build data model;

receiving or generating a set of configuration model definitions; and

building the bundled configuration data set comprising the bundle of configuration files by using (i) a plurality of build inputs based on a source path of the received one or more configuration source files and (ii) the set of configuration model definitions.

2. The system of claim 1 wherein the configuration model definitions define attribute schema, relationship parameters, and uniqueness constraints.

3. The system of claim 2 wherein the attribute schema describe validations and structure of a configuration entity, and wherein the relationship parameters describe how configuration entities interface.

4. The system of claim 1 wherein the building the bundled configuration data set comprises:

parsing the one or more configuration source files;

processing the parsed data to perform a validation from the set of configuration model definitions, wherein the validation includes using the set of configuration model definitions to ensure an identity and type of the data models are valid, and

inserting a validated data model into a configuration store of the non-transitory memory.

5. The system of claim 1 wherein the processor is configured to use metadata to validate the data represented in the one or more configuration source files, wherein the metadata includes structure and rules of a configuration process.

6. The system of claim 1 wherein the grouped file structure of the bundle of configuration files includes a serialization of the data represented in the received one or more configuration source files.

7. The system of claim 1 wherein the processor is configured to break down the artifact based on one or more domains to perform a validation check on one or both of structure of the data in the artifact and content of the data in the artifact.

8. The system of claim 1 wherein the enterprise software platform is directed to a supply chain management of a personalized medicine treatment comprising a plurality of stakeholder clients selected from a group consisting of a health care provider (HCP), a health care institution, a pharmaceutical manufacturer, a biological material manufacturer, a courier service, and a material storage service, and wherein the system is operable to introduce a new functionality of the supply chain management in the version of the software application of the enterprise software platform executable by the client computer.

9. The system of claim 8 wherein the system is operable to create a new node in the supply chain management of the personalized medicine treatment for a first client computer associated with one of the plurality of stakeholder clients while maintaining an existing version of the supply chain management for a second client computer associated with another of the plurality of stakeholder clients.

10. A method for automating client-specific software application configuration management for an enterprise software platform, the method comprising:

receiving, at a server in communication with at least one data store operating an enterprise software platform, data comprising one or more configuration source files associated with a software application of the enterprise software platform executable on a client computer, where the one or more configuration source files includes instructions for a set of configuration changes to a version of the software application executable on the client computer; and

processing, at the server, the received instructions for the set of configuration change, using (i) a set of schemas describing at least one of an organization criteria or a validation criteria associated with data structures of the at least one data store and (ii) a set of parameters describing rules governing how to interface with the data structures, to generate an artifact customized for the client computer, wherein the customized artifact comprises a bundle of configuration files configured in a grouped file structure; and

wherein the customized artifact is capable of transforming only the version of the software application executable on the client computer in accordance with the instructed set of configuration changes without introducing a change in a master version of the software application to the enterprise software platform executable on one or more other computers,

wherein the processing the received instructions for the set of configuration changes comprises:

initiating a build process to produce a bundled configuration data set based on the one or more configuration source files;

receiving or generating a canonical model of a build data model;

receiving or generating a set of configuration model definitions; and

building the bundled configuration data set comprising the bundle of configuration files by using (i) a plurality of build inputs based on a source path of the received one or more configuration source files and (ii) the set of configuration model definitions.

11. The method of claim 10 wherein the configuration model definitions define attribute schema, relationship parameters, and uniqueness constraints.

12. The method of claim 11 wherein the attribute schema describe validations and structure of a configuration entity, and wherein the relationship parameters describe how configuration entities interface.

13. The method of claim 10 wherein the building the bundled configuration data set comprises:

parsing the one or more configuration source files;

processing the parsed data to perform a validation from the set of configuration model definitions, wherein the validation includes using the set of configuration model definitions to ensure an identity and type of the data models are valid, and

inserting a validated data model into a configuration store of the non-transitory memory.

14. The method of claim 10 , further comprising:

at the server, using metadata to validate the data represented in the one or more configuration source files, wherein the metadata includes structure and rules of a configuration process.

15. The method of claim 10 wherein the grouped file structure of the bundle of configuration files includes a serialization of the data represented in the received one or more configuration source files.

16. The method of claim 10 , further comprising:

at the server, interrogating the artifact based on one or more domains to perform a validation check on one or both of structure of the data in the artifact and content of the data in the artifact.

17. The method of claim 10 wherein the enterprise software platform is directed to a supply chain management of a personalized medicine treatment comprising a plurality of stakeholder clients selected from a group consisting of a health care provider (HCP), a health care institution, a pharmaceutical manufacturer, a biological material manufacturer, a courier service, and a material storage service, and wherein implementation of the method by a stakeholder client operating the client computer introduces a new functionality of the supply chain management in the version of the software application of the enterprise software platform executable by the client computer.

18. The method of claim 17 comprising:

at the server, creating a new node in the supply chain management of the personalized medicine treatment for the stakeholder client operating the client computer by fulfilling the configuration change to the version of the software application of the enterprise software platform operated by the client computer while maintaining a present version of the supply chain management for another stakeholder client operating a second client computer executing the software application of the enterprise software platform.