Page History

page-info

:title}

caBIG® version 2.0 federated, semantically aware service-oriented architecture (sSOA) enables the development of a continuous and accelerated cycle of scientific discovery, diagnostics, pharmaceutical product development and improved clinical care. This supports diverse stakeholders

 -- from patients to providers, researchers to regulators, administrators to advocates

 -- and enables effective collaborations in ways never before possible.

Semantic Infrastructure 2.0 provides the underlying metadata and terminologies enabling interoperability on the sSOA. As such, semantic infrastructure most likely needs to address the entire breadth of the stakeholders that will be participating in the development of sSOA.

The semantic infrastructure stakeholder list below defines the initial list of stakeholders critical to the success of semantic infrastructure 2.0. The stakeholders list is being enhanced during the community review of the Semantic Infrastructure 2.0 Roadmap, to ensure that the list includes the breadth of the community that will be impacted by the Roadmap.

|| Stakeholder Category

 || Groups || Sub Groups || Primary/Targeted Engagement Option

 || Available

 Options ||
| Requester(s)

 | CBIIT

 Director | | One on One | |
| Requester(s)

 | NCI | Other NCI Divisions, programs or projects

 | Focused engagement through deployment and analysis teams

 | CVRG, BIRN, CTSA, caEHR

 |
| Requester(s)

 | Cancer Center/Community Center (NCCCP)

 | Early implementer site, seeking to adopt solution

 | Working with group as part of project activities

 | caBIG Deployment Activities

 |
| Requester(s)

 | Cancer Center/Community Center (NCCCP)

 | Early implementer site, seeking to adapt solution into their

 environment | | |
| Requester(s)

 | Cancer Center/Community Center (NCCCP)

 | Non-Early Adopter

 | No focused engagement

 -- standard

 engagement | |
| Requester(s)

 | Big Pharma

 | Interested Adopter (from previous engagement)

 | Working with group as part of project activities

 | Novartis (Imaging)

 |
| Payer(s)

 -- System | CBIIT Director | | One on One | |
| Payer(s)

 -- System | | | | |
| Payer(s)

 -- System | Implementers | Vendors or Sites which implement some or all components of PST will need to invest $. | Focused engagement through deployment & analysis teams | TBD |
| Users (Direct Users) | Curators | Metadata, terminology and forms curators | All engagement options (subject to group charter limits) | TBD |
| Users (Direct Users) | Service Developers | CBIIT sSOA developers | All engagement options (subject to group charter limits) | TBD |
| Users (Direct Users) | | Vendor Service developers | All engagement options (subject to group charter limits) | TBD |
| Users (Direct Users) | Application Developers | CBIIT Application, that is, service orcherstration, developers | All engagement options (subject to group charter limits) | TBD |
| Users (Direct Users) | Platform Developers | HealthCare IT Vendors | TBD | TBD |
| Users (Secondary) | Clinicians | Pathologists | Domain Governance | TBD |
| Users (Secondary) | | Radiation oncology expert | | |
| Users (Secondary) | | Disease or tumor registry SME | | |
| Users (Secondary) | | Pharmacists (with experience in an oncology focused setting) | | |
| Users (Secondary) | | Other professional groups | | |
| Users (Secondary) | Bioinformaticians | Science PI and Staff | Domain Governance | |
| Users (Secondary) | IT Staff | Deployment Staff | Working with group as part of project activities | |
| Users (Secondary) | System Administrators and Trainer | Infrastructure Staff | TBD | |
| Users (Secondary) | Information Systems Security Office (ISSO) | Deployment Staff | TBD | |
| Regulators | FDA | Compliance | | |
| Regulators | NIST | Certification criteria, Security Regulations, etc | | |
| Regulators | OMB | FISMA, CPIC, etc | | |
| Regulators | ONC | NHIN | Working with group as part of project activities | |
| Regulators | Privacy Officers | Data Sharing Group | | |
| Collaborators | SDOs | HL7 , CDISC , BRIDG Group , Object Management Group (OMG),   | Working with group as part of project activities | |
| Collaborators | | Federal standards bodies related to the overall ONC framework | See separate work re. groups in external communications strategy | |
| Collaborators | | International Standards Organization (ISO) , DICOM , W3C , Open Health Tools (OHT) , Other | Assigning analyst to monitor (as/when needed) | |
| Patients | Patient Advocacy Groups | | TBD | |
| Vendors | HealthCare IT Vendors | | TBD | |

Table 2.1 Semantic Infrastructure Stakeholder List

The table above identifies stakeholder roles based on stakeholder category, groups within each category, and further sub groups based on distinct roles. Note that individual members of the community may fill multiple roles simultaneously.

An initial engagement plan is provided in the "Planned/Targeted Engagement Option" column for each stakeholder to ensure that stakeholder input is appropriately captured in the effort. Options are identified in the next column, "Available Options."

Following are definitions of columns in the table:

*Stakeholder Category:* This defines the high level role of the stakeholder, which determines the type of engagement and interaction in the semantic infrastructure effort. The following stakeholder categories have been identified:
* Requester(s): This category consists of stakeholders that are primary decision makers in organizations, seeking to adopt semantic infrastructure in their organization.
* Payer(s) - System: This category consists of stakeholders that will be required to commit resources towards building semantic infrastructure
* Users (Direct Users) - This category consists of stakeholders that will be directly consuming the artifacts and solution developed by semantic infrastructure. Since the semantic infrastructure is the underlying IT platform, the primary users will be mainly technical users and will not be end users.
* Users (Secondary) - This category consists of stakeholders that will consume the artifacts produced by the direct users. These will be primarily end users, including but not limited to oncologists and bioinformaticians, who will interact indirectly with semantic infrastructure through the artifacts developed by technical users (direct users).
* Regulators: This category consists of stakeholders who create, implement, or both, policy guidelines that impact semantic infrastructure directly or indirectly.
* Collaborators: These are parties who are engaged in similar activity, where collaboration will help semantic infrastructure in reducing effort or provide an enhanced solution.
* Patients: This category consists of people who receive care and those who advocate on their behalf.
* Vendors: This category consists of health care IT vendors who will be consuming the open specifications developed by the semantic infrastructure team and provide their own interoperable implementations.

*Groups:* This defines different groups of stakeholders within a single stakeholder category, based on their role in the entire health care enterprise. (Refer to the table for the current list of groups.)

*Sub Groups:* Each group could be further subdivided into smaller sub groups, that would help determine an appropriate focused and targeted engagement plan, and ensure that the stakeholder requirements are considered at the tactical level. (Refer to the table for the current list of sub groups.)

*Primary/Targeted Engagement Option:* This column provides an initial engagement plan that would provide for getting stakeholder input to semantic infrastructure expeditiously . This will be enhanced in further drafts and based on guidance from community.

*Available Options:* These are ways available at the present time to provide for engagement.

{scrollbar:icons=false}