IO Specifications Publication Model

Table of Contents

Interoperability (IO) Specification Publication Model

	Specification Publication Types
Publication Attributes	Draft	Trial Implementation	Final
Implementation Readiness	In Development	Limited Roll-Out	Production
Prototyping / Validation Readiness	Beta Testing / Beta Projectathon	Projectathon / Conformance	Connectathon / Certification

IO Specification Publication Types

Draft

When this designation is assigned, the specification is currently in development and may be in the midst of an internal and/or public review period. These specifications will generally benefit from lessons learned through development and pilots.

Trial Implementation

When this designation is assigned, the specification is considered to be a draft for trial use / trial implementation in production systems. It has been cycled through public open review and comment dispositioning has been completed. In some cases, features and capabilities or known issues may be documented in the backlog for inclusion in a future trial implementation release.

Final

When this designation is assigned, the specification is considered to have addressed all stakeholder comments received in reviews of prior releases. Projectathon testing has been successfully completed, with all known issues resolved. And, all documentation is complete, providing implementers the ability to use the specification for compliance and certification of their products.

IO Specification Attribute Definitions

Implementation Readiness

In Development: when this designation is assigned, the specification is in the development process and subject to significant change. It is not ready for limited roll-out or production level use.
Limited Roll-Out: when this designation is assigned, the specification is ready to be used on a limited scale projects to meet a health care interoperability need.
Production: when this designation is assigned, the specification is ready to be used in production to meet a health care interoperability need.

Prototyping / Validation Readiness

Beta Testing / Beta Projectathon: when this designation is assigned the specification is subject to significant changes and has undergone feature complete testing by the Infoway IO team. The specification may be available to implementers to test their solutions at a testing event, such as a beta Projectathon, to provide input and help prepare the specification for Projectathon readiness.
Projectathon / Conformance: when this designation is assigned the specification is ready for testing and validation where implementers collaborate to test their solutions using methodology and tools that accelerate interoperability. A Projectathon provides an opportunity for participants to test their systems among themselves, against a reference environment and show conformance with the specification.
Connectathon / Certification: when this designation is assigned, the specification is ready for implementers to perform detailed validation and achieve certification of their solutions to the specification.

IO Specification Publication Versioning

The interoperability specifications will follow semantic versioning, using a three-part version number and release type tag (e.g., v0.1.0 DFT, v1.1.1 TI, etc.,).

Major:

Increments every time a breaking change is made.
Indicated by increasing the Major number.

Minor:

Increments every time new non-breaking changes are made (i.e., changes that create new capabilities, but do not render existing implementations to be non-conformant.
Indicated by increasing the Minor number.
Resets to 0 each time the Major version changes.

Patch:

Non-breaking changes (e.g., corrections).
Indicated by increasing the Patch number.
Resets to 0 each time the Minor version changes.

Release Tag:

Draft (DFT)
Trial Implementation (TI)
Final

IO Specification Publication Process Flow

Click on the image to view in full size.

IO Specification Publication Process Roles

Role	Description
IO Change Control Board	The Interoperability Change Control Board (CCB) will manage the evolution of the interoperability specifications, deciding on the priorities and content for upcoming releases, managing the backlog and roadmap milestones. The CCB will consist of Interoperability management , subject matter experts and representatives from the Operational and Strategic Governance bodies.
IO Team
Jurisdictional Partners
Public Stakeholders
Operational Governance
Strategic Governance

IO Specification Publication Process Example

The following table provides an example scenario of a specification flowing through the Interoperability Publication Process from the initial Draft through to its' Final release.

Draft	TI	Final	Description
0.1.0 DFT			Draft releases: First release
0.2.0 - 0.3.0 DFT			Draft releases: Specifications will evolve through multiple Draft versions, which will be available for open public review and may be validated in prototyping events (e.g., Projectathon) to assist in the stability of the specifications and ability to transition to Trial Implementation.
	1.0.0 TI		Trial Implementation: First Major release Specifications may be validated in prototyping events (e.g., Projectathon). Input from jurisdictions and other stakeholders (e.g., vendors, PCHO's), the backlog & roadmap will inform future releases. If additional corrections and/or enhancements are required, the cycle will begin again in Draft.
1.0.1 DFT			Draft release: A correction is identified as a required change to the v1.0.0 TI release. Note: for patch corrections (e.g. typos, description updates), the specification may not go into open review.
	1.0.1 TI		Update to the Trial Implementation release: correction update included. v1.0.1 released to the public and implemented by the market.
1.1.0 - 1.11.0 DFT			Draft releases: Including new development towards the next Trial Implementation (i.e., IO Program continues to plan and develop backlog and roadmap items.)
	1.11.0 TI		Trial Implementation: Minor update (i.e., includes enhancements developed and tested in Draft versions 0.5.0 - 0.11.0). Note: v1.1.0 may supersede 1.0.1.
1.12.0 DFT			Draft: First draft of a new Minor release
1.13.0 - 1.15.0 DFT			Draft: Subsequent drafts in preparation for the next Trial Implementation Major release Specifications will evolve through multiple Draft versions, which will be available for open public review and may be validated in prototyping events (e.g., Projectathon) to assist in the stability of the specifications and ability to transition to the next Trial Implementation release.
	2.0.0 TI		Trial Implementation: Second TI release. Note v2.0.0 TI may co-exist with v1.1.0 TI, depending on market adoption of v1.1.0 TI. Input from governance, jurisdictions and other stakeholders (e.g., implementers, PCHO's), the backlog & roadmap will inform future releases. At such time where no further changes are required, the TI release will be deemed ready to transition to the Final version. Until such time, the cycle of Draft - Trial Implementation releases will continue.
		Release 1 Final	Final release: v1.0 Final is based on v2.0.0 TI Specifications deemed as Final are ready for implementers to use for compliance / certification. The Final version is not intended to change. Note: For newly emerging capabilities / features, the specification cycle would begin again with a Draft version.

Page tree