 |
Page History
| Wiki Markup |
|---|
{scrollbar}
{children}
h3. { |
| Scrollbar |
|---|
| Children Display |
|---|
page-info |
...
Summary
Description of the profile
The use of well defined service metadata promotes better discovery and reuse of services during design.
Capabilities
Requirements traceability
...
Requirement
...
Source
...
Capability
...
Query and retrieve Value Sets
...
:title} h4. Summary h5. Description of the profile The use of well defined service metadata promotes better discovery and reuse of services during design. h5. Capabilities * [integrativeAnalysis|#EAID_3B8EB478_F3A5_402b_8297_EB046ADA8DA1] * [queryValueSets|#EAID_65B6CC74_7AA9_4427_A3ED_FDC961514F4D] h4. Requirements traceability ||Requirement||Source||Capability|| |Query and retrieve Value Sets |Gap Analysis::Analyze:: |
...
{anchor |
...
:_16_5_1_24a0131_1283082518100_711251_4179 |
...
...
Support integrative analysis across multiple disciplines
...
}126 - Query and retrieve Value Sets|{li}[queryValueSets|#EAID_65B6CC74_7AA9_4427_A3ED_FDC961514F4D]{li}| |Support integrative analysis across multiple disciplines |Gap Analysis::Analyze:: |
...
{anchor |
...
:_16_5_1_24a0131_1283082572145_489198_4182 |
...
...
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy. A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets. Requirements include: * Query and retrieve Value Sets * Support integrative analysis across multiple disciplines * Query and aggregate data across organizations, data sets, time, and geographies. * Integrate clinical trial data with health record data. By multiple data sets CDISC means different clinical trials, data sets from different EHR systems, and the interoperability of clinical trial and EHR data sets. At a minimum the Knowledge Repository should be able to identify those data sets that are constructed from or map to the Knowledge Repository's information models, model elements, and alignment assertions among these models. Thus, an approved alignment between a local information model and (for example) a specific CDISC standard would be an assertion that new models could map to. This linkage from the KR to specific data sets that instantiate information models sets the stage for full model analysis.
...
}146 - Support integrative analysis across multiple disciplines |{li}[integrativeAnalysis|#EAID_3B8EB478_F3A5_402b_8297_EB046ADA8DA1]{li}| |The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy. A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets. Requirements include: * Query and retrieve Value Sets * Support integrative analysis across multiple disciplines * Query and aggregate data across organizations, data sets, time, and geographies. * Integrate clinical trial data with health record data. By multiple data sets CDISC means different clinical trials, data sets from different EHR systems, and the interoperability of clinical trial and EHR data sets. At a minimum the Knowledge Repository should be able to identify those data sets that are constructed from or map to the Knowledge Repository's information models, model elements, and alignment assertions among these models. Thus, an approved alignment between a local information model and (for example) a specific CDISC standard would be an assertion that new models could map to. This linkage from the KR to specific data sets that instantiate information models sets the stage for full model analysis. |Semantic Infrastructure Requirements::Service Discovery and Governance::{anchor:_16_5_1_24a0131_1283090102585_533218_4554 |
...
queryValueSets, integrativeAnalysis,
...
A key long-term CDISC business goal is to integrate Clinical Trial Data with Electronic Health Record (EHR) data. These two types of data sets collect similar data about individuals in order to diagnose and treat disease. This integration would allow much larger data sets to be explored on the outcomes of specific treatment on a diverse range of individuals. The clinical data set form naturally occurring "experiments," and allows the longer term observation of approved treatments as well as off-label treatments. This would start to integrate medical care from (research) bench to (patient) bed.
...
}Analyze Services|{li}[queryValueSets|#EAID_65B6CC74_7AA9_4427_A3ED_FDC961514F4D]{li}{li}[integrativeAnalysis|#EAID_3B8EB478_F3A5_402b_8297_EB046ADA8DA1]{li}| |A key long-term CDISC business goal is to integrate Clinical Trial Data with Electronic Health Record (EHR) data. These two types of data sets collect similar data about individuals in order to diagnose and treat disease. This integration would allow much larger data sets to be explored on the outcomes of specific treatment on a diverse range of individuals. The clinical data set form naturally occurring "experiments," and allows the longer term observation of approved treatments as well as off-label treatments. This would start to integrate medical care from (research) bench to (patient) bed. |Gap Analysis::CDISC::{anchor:_16_5_1_24a0131_1283075780822_64155_4062 |
...
}CDISC-19 - Use CDISC standards to integrate clinical trial data with health record data |
...
...
|{li}[integrativeAnalysis|#EAID_3B8EB478_F3A5_402b_8297_EB046ADA8DA1 |
...
]{li}| h4. {anchor:EAID_3B8EB478_F3A5_402b_8297_EB046ADA8DA1 |
...
Description
Support integrative analysis across multiple disciplines
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy.
A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets.
Integrate clinical trial data with health record data.
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy.
A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets.
Requirements addressed
- CDISC-19 - Use CDISC standards to integrate clinical trial data with health record data
- Analyze Services
- 146 - Support integrative analysis across multiple disciplines
Overview of possible operations
...
}integrativeAnalysis h5. Description Support integrative analysis across multiple disciplines The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy. A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets. Integrate clinical trial data with health record data. The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy. A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets. h5. Requirements addressed * [Analyze Services|#_16_5_1_24a0131_1283090102585_533218_4554] * [146 - Support integrative analysis across multiple disciplines |#_16_5_1_24a0131_1283082572145_489198_4182] * [CDISC-19 - Use CDISC standards to integrate clinical trial data with health record data|#_16_5_1_24a0131_1283075780822_64155_4062] h5. Overview of possible operations h4. {anchor:EAID_65B6CC74_7AA9_4427_A3ED_FDC961514F4D |
...
Description
Query and retrieve Value Sets
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy.
A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets.
Requirements addressed
Overview of possible operations
...
}queryValueSets
h5. Description
Query and retrieve Value Sets
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy.
A capability to analyze data was explicitly cited as a critical goal by CDISC and caEHR stakeholders. From the perspective of the KR, this requirement should perhaps be entitled “Enable Data Integration through Model Alignment,” since it allows users to provide the metadata necessary to enable integration of heterogeneous data sets.
h5. Requirements addressed
* [Analyze Services|#_16_5_1_24a0131_1283090102585_533218_4554]
* [126 - Query and retrieve Value Sets|#_16_5_1_24a0131_1283082518100_711251_4179]
h5. Overview of possible operations
{scrollbar}
|
