What’s the difference between iSHARE and eSHARE?


CDISC SHARE is a metadata repository (MDR) that supports the development, governance, publishing, and consumption of the CDISC standards in human and machine-readable formats. For more information about SHARE see the CDISC Website. eSHARE and iSHARE are parts of the overall SHARE system. They represent two separate ways to access SHARE content, as shown in the diagram below.

Interactive SHARE, or iSHARE, is the tool used by the CDISC standards development community for developing, governing, and publishing the standards. iSHARE is a cloud-based MDR configured for the CDISC standards that includes a number of standards management and development tools. Prior to accessing the tool, CDISC standards team members receive both on-line and interactive iSHARE training. Each standards development project works with the SHARE Metadata Curators to create and publish new CDISC standards. As new standards, and new versions of existing standards, are created iSHARE provides tools for exporting the standards content in a number of machine-readable formats.

Exports from SHARE, or eSHARE, is a website that has the standards published from iSHARE available for easy download. The eSHARE site serves subscribers that implement the CDISC standards. eSHARE content will be available in multiple formats and multiple versions. The eSHARE content reflects published content available for export in iSHARE. Interim work-in-progress versions of a standard will not typically be published to eSHARE since they are not intended for production use. While CDISC will demonstrate the proper use of eSHARE, no formal training is required. eSHARE subscribers will have the option of receiving email notifications when new content is posted for download. eSHARE content will largely be centered on machine-readable versions of the CDISC standards metadata.

For the initial SHARE release versions of SDTM and CDASH were loaded, along with the CDISC Controlled Terminology and the BRIDG model. During the next release the SHARE team is loading content from the remaining foundational standards, in addition to updating existing content. Standards content exports will be made available for download via eSHARE in machine-readable formats, including:  ODM, Define-XML, Excel/CSV, and RDF/OWL.

Both iSHARE user and eSHARE users will be required to agree to basic licensing terms. iSHARE is based on a commercial software tool, and a license is required prior to receiving an account on the system. eSHARE access requires a subscription, and the very first subscribers will be the CDISC platinum members.

In sum, the CDISC standards teams use iSHARE to develop standards, and organizations that implement the standards use eSHARE to access machine-readable standards metadata. See the SHARE FAQ for more information on iSHARE and eSHARE. In the future, iSHARE access may be opened up to a broader community that seeks to leverage iSHARE tools to analyze standards content. CDISC also anticipates working with software tool developers to enable automated syndication of SHARE content to participating vendor applications.

Comments

  1. UnknownJune 3, 2014 at 10:38 AM

    Hi Sam, great work and nice blog!
    Very good to see semantic web versions of CDISC standards from eSHARE. A couple of questions:

    - Will you use the schemas RDF schemas https://github.com/phuse-org/rdf.cdisc.org/tree/master/schemas developed by the FDA/PhUSE Semantic Technology project http://www.phusewiki.org/wiki/index.php?title=Semantic_Technology ? If so, there are some opportunities to apply learnings to improve these schemas based on the experiences from representing CDISC fundamental standard https://github.com/phuse-org/rdf.cdisc.org/tree/master/std s.

    - What formats are you planning to serialize the RDF modelled data exports in? The experiences from many semantic web/linked data projects are that Turtle (ttl) and JSON-LD version are preferred by developers over XML.

    - Any plans to provide a URI resolver service for individual standards items, e.g. resolve the URI for the VSTESTCD data element to a URL for with the descriptions of it and links to other items, as supplement to bulk exports?

    KUTGW

    ReplyDelete
    Replies
    1. Sam Hume, DScAugust 6, 2014 at 7:29 AM

      Thanks Kerstin. The public review period for the CDISC standards in RDF will begin soon. Please submit you comments so they're part of the official review. We'll likely look to setup a meeting with you to discuss them further. I believe the serialization format will be Turtle. There are no current plans for a URI resolver service, but this would make a good comment during the public review.

      Delete

Post a Comment

Popular posts from this blog

ODMv2: Renovating the ODM Standard

  ODM, CDISC's Operational Data Model , version 1.x will be 17 years old in October, making it a mature standard. ODM has come of age , and it's time for ODM to take on a bit more responsibility around here. Toward this end, a new XML Technologies development team has recently started work on ODMv2, a substantially updated version of ODM that breaks backwards compatibility with version 1.3.x to add a number of significant new features. This post highlights some areas of new development for ODMv2. As ODMv2 is still in the early stages of development, the scope of the project and specific features are subject to change. Among the more important new ODMv2 features will be a RESTful API that specifies standard methods of data and metadata exchange. The RESTful architecture uses specific URLs and the HTTP protocol to leverage pervasive, scalable web technologies to simplify data interchange. Lack of a common API for data exchange in clinical research has limited the available...
Read more

Value Level Metadata, Vertically Structured Datasets, and Normalizaton

Image
As part of the work to implement Value Level Metadata in SHARE, as well as to author a Define-XML Implementation Guide article, this will be the first of a series of posts on the topic of Value Level Metadata. These posts target a more technical audience, however the Define-XML IG article will include less technical jargon. Future posts will cover additional Value Level Metadata topics and examples. Value Level Metadata (VLM) is metadata that constrains a variable definition based on the value of another variable(s). VLM was originally specified in Define-XML v1.0 as a mechanism for providing the additional metadata needed for software to more accurately interpret these constrained variables.  For example, VSORRES is a variable with structural metadata of  DataType=”Text” and Length=”200”. However, when VSTESTCD=”DIABP” that definition is constrained by VLM to use DataType=”integer” and Length="3". In this case, the value of DIABP in VSTESTCD has triggered the application o...
Read more

CDISC ODMv2 Development Progress: A 2018 Q1 Update

Image
Since starting work on ODMv2 last year the CDISC Data Exchange Standards Team, formerly known as the XML Technologies Team, has made substantial progress towards completing the backlog tasks and updates planned for ODMv2. Much of this work is progressing concurrently, creating a broad set of ongoing discussions. To follow the ODMv2 development work the best place to begin is the ODM-XML page in the XML Tech space on the CDISC Wiki, where you can find a list of the most recently updated pages, a link to the decision log, and links to other relevant aspects of the project. You can also find the notes from our meetings, and if you miss a meeting, a recording of it is available through the notes for a few weeks after the teleconference. The Data Exchange Standards Team's goal for 2018 is to release a first draft of ODMv2 for trial use by the end of year. We then plan to test and revise the draft for final release during 2019. This post, some of which was included in the Q4 201...
Read more