SHARE R1 is Done

SHARE is no longer merely a vision, idea, or plan. After nearly 6 months of implementation work SHARE R1, our first production library, has been completed. Woot woot! This is a major milestone. We've taken the first step on a long journey towards realizing the vision of transforming the CDISC standards into an end-to-end, interoperable set of metadata all available in a machine-readable format.

Both SDTM 1.2 (IG 3.1.2) and CDASH 1.1 have both been loaded into the production SHARE Library. Using SHARE R1 we will load SDTM 1.3 (IG 3.1.3) and SDTM 1.4 (IG 3.2) in the coming weeks. Although the CDISC Controlled Terminology development and governance processes will remain unchanged, we will continue to load each newly released terminology package into SHARE. BRIDG 3.2 and the ISO 20190 data types have also been loaded into the R1 library.

The theme for R1 was Machine-Readable Standards. The SHARE Team plans to publish metadata from SHARE for subscribers to download by the end of Q1 2014. The metadata will be published from SHARE in a number of machine-readable formats, including Define-XML, ODM, Excel, and later this year RDF. The published metadata will be posted to a web site for subscribers to download.

Initially most users will access published SHARE content using the download site. This provides easy access to machine-readable standards published from the SHARE production library. In the near term, only those developing and governing the standards will use the SHARE software interactively. As we adjust to the new standards development processes, and load more standards content into SHARE, we will slowly grow the community of interactive SHARE users.


Now that R1 is in our rear view mirror, we’re about to begin the R2 journey. R2 is themed the SHARE Concept Model and will run through the end of 2014. R2 will focus developing the SHARE concept model, as well as loading the remaining CDISC standards metadata into the production library. Thanks to all who helped make our first production library possible. The SHARE Team is looking forward to starting work on R2.

Comments

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