Page History
Wiki Markup |
---|
{scrollbar}
{children}
h3. { |
Scrollbar |
---|
Children Display |
---|
page-info |
...
Summary
Description of the 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.
Capabilities
Requirements traceability
...
Requirement
...
Source
...
Capability
...
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
...
:title} h4. Summary h5. Description of the 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. h5. Capabilities * [cdiscFormGenModel|#_16_5_1_24a0131_1283190278677_703658_6346] * [serviceGenModel|#_16_5_1_24a0131_1283167399564_196240_3070] h4. Requirements traceability ||Requirement||Source||Capability|| |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 |Gap Analysis::CDISC::{anchor:_16_5_1_24a0131_1283075778144_701006_4050 |
...
}CDISC-15 - Support generating standards-based data collection forms |
...
...
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.
...
|{li}[cdiscFormGenModel|#_16_5_1_24a0131_1283190278677_703658_6346]{li}| |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. |Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::{anchor:_16_5_1_24a0131_1283090073806_566470_4527 |
...
...
}Service Generation|{li}[serviceGenModel|#_16_5_1_24a0131_ |
...
1283167399564_ |
...
196240_3070]{li}| h4. {anchor:_16_5_1_24a0131_1283190278677_703658_6346 |
...
Description
CDISC Form Generation Model API
...
}cdiscFormGenModel h5. Description 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. |
...
h5. Requirements |
...
addressed * [CDISC-15 - Support generating standards-based data collection |
...
Overview of possible operations
...
forms|#_16_5_1_24a0131_ |
...
1283075778144_ |
...
701006_4050] h5. Overview of possible operations h4. {anchor:_16_5_1_24a0131_1283167399564_196240_3070 |
...
Description
Service Discovery Model API
Requirements addressed
Overview of possible operations
...
}serviceGenModel
h5. Description
Service Discovery Model API
h5. Requirements addressed
* [Service Generation|#_16_5_1_24a0131_1283090073806_566470_4527]
h5. Overview of possible operations
{scrollbar} |