Define-XML



Define-XML Courses






Statement:

Supporting automation for implementation of CDISC Foundational standards is a fundamental requirement for Data Exchange Standards development.

Rationale:

From the beginning, the Data Exchange Standards have been harmonized with CDISC Foundational standards.

Key Benefits:

Reduces cost and improves efficiency for CDISC implementers.

Statement:

Data Exchanges Standards should reuse XML components from the ODM and other CDISC extensions when usage is aligned with the semantics.

Rationale:

The ODM has already been aligned with BRIDG.

Key Benefits:

Parsimonious models are more efficient.

Statement:

The Data Exchange Standards are developed following an agile development process.

Rationale:

Agile is widely recognized as a software development best practice.

Key Benefits:
  • New versions are more frequent and with fewer changes.
  • Effort for adopting a new version will be less.
  • New versions reflect most urgent needs identified by implementers.
Statement:

Define as much of the standard through the XML Schema as possible.

Rationale:

Leverage XML technology as much as possible. This may include related technologies like Json.

Key Benefits:

Enables implementers to leverage widely available low-cost tools and encourages collaboration with organizations working with other health care/biomedical science standards.

Statement:

Ensure our Data Exchange Standards are clearly documented.

Rationale:

Many programmers will need to implement XML Technology standards without attending a training class.

Key Benefits:

The quality of documents following the Data Exchange Standards will be consistent. This is important for encouraging new implementations.