Page tree
Skip to end of metadata
Go to start of metadata




1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1b. Project ID

1647

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?

Yes

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1h. ISO/IEC Standard to Adopt

Nil

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Service Oriented Architecture

2d. Project Facilitator

Vincent McCauley

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

2g. Publishing Facilitator

Lorraine Constable

2h. Vocabulary Facilitator

2i. Domain Expert Representative

Stefano Lotti

2j. Business Requirements Analyst

2k. Conformance Facilitator

2l. Other Facilitators

2m. Implementers

Mayo Clinic, PHAST (France), Fraunhofer FOKUS (Germany), OMG, Telstra Health (Australia))

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

Attachments

3b. Project Need

The CTS2 Standard requires reaffirmation. CTS2 provides a standardized interface for the use and management of terminologies. CTS2 provides a modular, common, and universally deployable set of behaviors which can be used to manage sets of terminologies deployed in a service environment. CTS2 services contribute to interoperability by supporting easy access to the foundational elements of shared semantics and foster the authoring of high-quality terminologies via its authoring profile. Additionally. CTS2 defines the functional requirements of a set of service interfaces that allow the representation, access, and maintenance of terminology content either locally, or across a federation of terminology service nodes.

3c. Security Risk

No

3d. External Drivers

ANSI requirement for reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3f. Common Names / Keywords / Aliases:

"V3 Common Terminology Services, Release 2", CTS2, CTS 2, CTS

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/implement/standards/la.cfm?file=/documentcenter/private/standards/CTS/v3_cts2_r2_2015feb.pdf

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

N/A

3l. Reason for not using current V3 data types?

3m. External Vocabularies

N/A

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Reaffirmation of a standard

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?

5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

5b. Project Ballot Type

Normative (no STU)

5c. Additional Ballot Info

5d. Joint Copyright

No

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6f. Other Stakeholders

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6g. Other Vendors

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

7b. Sponsoring WG Approval Date

Jul 20, 2020

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

Sep 22, 2020

7j. TSC Approval Date



 Show Changes

Version

5

Modifier

Paul Knapp

Modify Date

Sep 22, 2020 16:33

1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1b. Project ID

1647

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

Yes

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1h. ISO/IEC Standard to Adopt

Nil

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Vincent McCauley

2g. Publishing Facilitator

Lorraine Constable

2i. Domain Expert Representative

Stefano Lotti

2m. Implementers

Mayo Clinic, PHAST (France), Fraunhofer FOKUS (Germany), OMG, Telstra Health (Australia))

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

3b. Project Need

The CTS2 Standard requires reaffirmation. CTS2 provides a standardized interface for the use and management of terminologies. CTS2 provides a modular, common, and universally deployable set of behaviors which can be used to manage sets of terminologies deployed in a service environment. CTS2 services contribute to interoperability by supporting easy access to the foundational elements of shared semantics and foster the authoring of high-quality terminologies via its authoring profile. Additionally. CTS2 defines the functional requirements of a set of service interfaces that allow the representation, access, and maintenance of terminology content either locally, or across a federation of terminology service nodes.

3c. Security Risk

No

3d. External Drivers

ANSI requirement for reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3f. Common Names / Keywords / Aliases:

"V3 Common Terminology Services, Release 2", CTS2, CTS 2, CTS

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/implement/standards/la.cfm?file=/documentcenter/private/standards/CTS/v3_cts2_r2_2015feb.pdf

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

N/A

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7b. Sponsoring WG Approval Date

Jul 20, 2020

7i. Steering Division Approval Date

Sep 22, 2020

Version

4

Modifier

Vincent McCauley

Modify Date

Aug 07, 2020 05:21

1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1b. Project ID

1647

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

Yes

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1h. ISO/IEC Standard to Adopt

Nil

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Vincent McCauley

2g. Publishing Facilitator

Lorraine Constable

2i. Domain Expert Representative

Stefano Lotti

2m. Implementers

Mayo Clinic, PHAST (France), Fraunhofer FOKUS (Germany), OMG, Telstra Health (Australia))

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

3b. Project Need

The CTS2 Standard requires reaffirmation. CTS2 provides a standardized interface for the use and management of terminologies. CTS2 provides a modular, common, and universally deployable set of behaviors which can be used to manage sets of terminologies deployed in a service environment. CTS2 services contribute to interoperability by supporting easy access to the foundational elements of shared semantics and foster the authoring of high-quality terminologies via its authoring profile. Additionally. CTS2 defines the functional requirements of a set of service interfaces that allow the representation, access, and maintenance of terminology content either locally, or across a federation of terminology service nodes.

3c. Security Risk

No

3d. External Drivers

ANSI requirement for reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3f. Common Names / Keywords / Aliases:

"V3 Common Terminology Services, Release 2", CTS2, CTS 2, CTS

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/implement/standards/la.cfm?file=/documentcenter/private/standards/CTS/v3_cts2_r2_2015feb.pdf

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

N/A

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7b. Sponsoring WG Approval Date

Jul 20, 2020

Version

3

Modifier

Dave Hamill

Modify Date

Aug 06, 2020 14:15

1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1b. Project ID

1647

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Vincent McCauley

2g. Publishing Facilitator

Lorraine Constable

2i. Domain Expert Representative

Stefano Lotti

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

3b. Project Need

Standard requires reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

N/A

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

Version

2

Modifier

Vincent McCauley

Modify Date

Jul 28, 2020 02:57

1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Vincent McCauley

2g. Publishing Facilitator

Lorraine Constable

2i. Domain Expert Representative

Stefano Lotti

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

3b. Project Need

Standard requires reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

N/A

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

Version

1

Modifier

Vincent McCauley

Modify Date

Jul 28, 2020 02:57

1a. Project Name

Clinical Terminology Service Revision 2 (CTS2) Reaffirmation

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

1e. Today's Date

Jul 28, 2020

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2

1g. Project Artifact Information

A project artifact is balloting Normative (no STU) (this includes reaffirmations)

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

No

1j. Unit of Measure

N/A (no measurements are in the standard

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Vincent McCauley

2g. Publishing Facilitator

Lorraine Constable

2i. Domain Expert Representative

Stefano Lotti

3a. Project Scope

Reaffirm the Clinical Terminology Service Revision 2 standard - a Service Oriented Architecture (SOA) Platform Independent Model (PIM) for clinical terminology provision and management

3b. Project Need

Standard requires reaffirmation

3e. Objectives/Deliverables and Target Dates

Reaffirmation January 2021 Ballot cycle

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

N/A

3o. Earliest prior release and/or version to which the compatibility applies

27 Feb 2015

4a. Products

V3 Services – Web Services (SOA)

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

6a. External Project Collaboration

OMG under Health Services Specification Project (HSSP) MOU

6b. Content Already Developed

100

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs)

6g. Vendors

Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6h. Providers

Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal