Service Generation Functional Profile
Service generation is the ability to generate services from user defined service metadata. The semantic infrastructure provides this metadata and the platform leverages this metadata for service generation. The constraints and policies specified in the semantic infrastructure are inherited by the platform and are enforced as runtime policies.
Additional platform specific and runtime information is provided by the developer at the time of service generation.
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
- Gap Analysis::CDISC::CDISC-15 - Support generating standards-based data collection forms In the medium-term (3-to-5 years) CDISC is interested in generating CDISC-standards based data collection forms (e.g., Case Report Form). Ideally data capture forms and the data captured by devices would follow CDISC standards. When data is submitted to a regulatory agency, (e.g., FDA), the compliance of this data with CDISC standards should be validated. Data collected using CDISC standards should have Computer Semantic Interoperability (CSI). However, this is not a current requirement; but the Knowledge Repository update of NCI Forms may provide this capability. *Source: * * 5/20/2010 Interview, Rhonda Facile * 06/09/2010 CDISC Share F2F Meetings, David Iberson-Hurst
- Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Service Generation Service generation is the ability to generate services from user defined service metadata. The semantic infrastructure provides this metadata and the platform leverages this metadata for service generation. The constraints and policies specified in the semantic infrastructure are inherited by the platform and are enforced as runtime policies. Additional platform specific and runtime information is provided by the developer at the time of service generation.
serviceGenModel
Service Discovery Model API
cdiscFormGenModel
CDISC Form Generation Model API
In the medium-term (3-to-5 years) CDISC is interested in generating CDISC-standards based data collection forms (e.g., Case Report Form). Ideally data capture forms and the data captured by devices would follow CDISC standards. When data is submitted to a regulatory agency, (e.g., FDA), the compliance of this data with CDISC standards should be validated. Data collected using CDISC standards should have Computer Semantic Interoperability (CSI). However, this is not a current requirement; but the Knowledge Repository update of NCI Forms may provide this capability.
