Page History

...

• Semantic Infrastructure Users and Roles
• Functional Requirements
  • Artifact Management
    • Static Models
    • Behavioral Models
    • Forms
    • Specification Content
  • Service Discovery & Governance
    • Discovery
    • Lifecycle Management
    • Governance
  • Case Report Form Modeling
    • Form template authoring
  • Conformance Testing
  • P/S/T caGRID 2.0 Platform & Terminology Integration
    

...

• Artifact Management
• Service Discovery and Governance
• Forms Defintion & Modeling
• Conformance Testing
• P/S/T caGRID 2.0 Platform & Terminology Integration

...

Other National Initiatives: All EHR vendors and national initiatives rely on a services paradigm for integration and interoperability. A standadized services metamodel makes it easier for participating organization to discover and reuse services.

caGRID 2.0 P/S/TPlatform: The caGRID 2.0 P/S/T provides Platform provides a runtime registry for service discovery. This service registry relies on a small subset of information for discovery. The semantic infrastructure provides a mechanism to leverage rich service and artifact metadata to extend this capability.

...

• CBIIT's adoption of ECCF: ECCF requires all specification developers to make conformance statements, the conformance testing framework leverages these conformance statements to generate validation tests
• ..
  

...

caGRID 2.0 Platform and Terminology Integration

The Semantic Infrastructure has to support seamless integration with the caGRID 2.0 P/S/T. The following are some high-level P/S/T and terminology requirements that either supported or addressed by the semantic infrastructure: 

...

Link to use case satisfied from P/S/T roadmapfrom caGRID 2.0 roadmap: As institutions share de-identified glioblastoma data sets, they are available to others via data discovery. The treatment recommendation service used by the oncologist is able to discover these new data sets and their corresponding information models, and include that data for subsequent use in recommendation of treatment.

Link to use case satisfied from P/S/T roadmapfrom caGRID 2.0 roadmap: all of the data management and access services in the use case are utilized by application developers to build the user interfaces that the clinicians use during the course of patient care.

...

Link to use case satisfied from P/S/T roadmapfrom caGRID 2.0 roadmap: Federated query over the TCGA data and other data sets is performed using a service orchestration.

...

Policy and Rules Management allow non-developer secondary users to create policies and rules and apply them to services. The scope of policies includes, but is not limited to, definition and configuration of business processing policy and related rules, compliance policies, quality of service policies, and security policies. Some key functional requirements to manage policies include capabilities to author policies and store policies, and for approval, validation, and run-time execution of policies.

The semantic infrastructure will provide a mechanism to specify policies, incuding business processing policy and related rules, compliance policies, quality of service policies. Tools and services for creating security specific policies will be provided by the caGRID 2.0 platform and will be used by the semantic infrastructure. All other policies specified inthe semantic infrastructure will be enforced by the platform at runtime.

Link to use case satisfied from caGRID 2.0 roadmap: Each institution has different data sharing needs, access control needs, and business rules for processing that are defined and customized. For Link to use case satisfied from P/S/T: Each institution has different data sharing needs, access control needs, and business rules for processing that are defined and customized. For example, policy at the pathologist's institution may state that the patient is scheduled for a visit when the review is complete.

...

Event Processing and Notifications enables monitoring of services in the ecosystem and provides for asynchronous updates by services, effectively allowing a loose coordination of services that both provide and respond to conditions (possibly defined in business rules).

The semantic infrastructure will provide a placeholder to specify events and triggering conditions for data and services, the platform monitors these events at runtime and acts on these events.

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: As patient care proceeds, the system notifies the designated clinicians that data (for example, images) are ready for review. Similarly, when notifications are received, event processing logic allows the appropriate parties to assign clinicians for care. In order to facilitate better treatment (a learning healthcare system), as new de-identified glioblastoma data is made available, notifications are sent that could indicate a recommended change in the treatment plan.

...

This set of requirements includes providing an application developer with the ability to define application-specific data elements and attributes (for example., defined using ISO 21090 healthcare datatypes) and an information model that defines the relationships between these data elements and attributes and other data elements and attributes in the broader ecosystem. In particular, the last requirement suggests linked datasets, where application developers can connect data in disparate repositories as if the repositories are part of a larger federated data ecosystem. Additional requirements include the ability to publish and discover information models. Support is needed for forms data and common clinical document standards, such as HL7 CDA. To support the use of binary data throughout the system, the binary data must be typed and semantically annotatedbe typed and semantically annotated.

All Information models, their represenation and binding to datatypes/terminologies will be managed by the semantic infrastructure. The ability to publish and disover information models will be supported by the semantic infrastructure and the platform will leverage these capabilities.

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: The pathology, radiology and other data have various data formats which must be described, and the information model for the patient record must link between these various datatypes. The complete information model includes semantic links between datasets to build a comprehensive electronic medical record. Annotations on data are defined and included in the information model.

...

Data management includes linking of disparate data sets and updates of data across the ecosystem. Data updates may include updates to multiple data sources, necessitating the need for transactions.updates may include updates to multiple data sources, necessitating the need for transactions.

Linkages between the different disparate data sets will be managed by the semantic infrastructure. Data upates that trigger transactions are captured by the platform and propogated upstream to the semantic infrastructure

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: the patient has an electronic medical record that spans multiple institutions. The clinical workup data (for example, genomics and proteomics data) is linked to the clinical care record; similarly pathology and radiology findings must be attached to the patient's electronic medical record.

...

The wealth of data must be accessible, resulting in the need for exploration of available datasets. This includes the ability to view seamlessly across independent data sets, allowing a secondary user to integrate data from multiple sources. In addition, the query capability must support sophisticated queries such as temporal queries and spatial queries.

The semantic infrastructure will provide metadata for discovery of these datasets, complex temporal and spatial queries will be informed by the metadata but will be formulated and exectured by the platform.

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: The oncologist must be able to quickly find glioblastoma data sets, indicating the fields that he is interested in comparing from his clinical data in order to find similar disease conditions and associated treatment plans. Temporal queries allow clinicians to identify changes in patient condition and treatment over time.

...

Provenance encompasses the origin and traceability of data throughout an ecosystem. This is a clear requirement directly from the use case in order to ensure that all steps of patient care and research are clearly linked via the patient record.

The semantic infrastructure will provide data provenance support.

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: The origin of data is tied to the data creator, allowing the oncologist performing the match against TCGA data and other datasets to include and exclude data sets based on their origin.

...

In a diverse information environment, semantics must be used to clearly indicate the meaning of data. This requirement is expected to be addressed by the Semantics Infrastructure, although there will be a touchpoint between the caGrid 2.0 and the semantics infrastructure to annotate data with semantics. Integration with the semantics infrastructure will enable reasoning, semantic query, data mediation (for example, ad hoc data transformation) and other powerful capabilities.

Data Semantic are captured in the semantic infrastructure,

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: The oncologist accesses the TCGA database to search for de-identified glioblastoma tumor data that is similar to the patient data exported from the hospital medical record. During this search, the semantics of the data fields are leveraged to indicate matches between TCGA data fields and the hospital medical record data fields.

...

Link to use case satisfied from P/S/Tfrom caGRID 2.0 roadmap: The oncologist searches both TCGA glioblastoma data as well as de-identified data that has been added by care providers around the country. The additional data sets are external data repositories.

...