Skip to end of metadata
Go to start of metadata




1a. Project Name

Reaffirmation of HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

1b. Project ID

1784

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?

No

1e. Today's Date

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

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?

1j. Unit of Measure

2a. Primary/Sponsor WG

Financial Management

2d. Project Facilitator

Paul Knapp

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

2g. Publishing Facilitator

Paul Knapp

2h. Vocabulary Facilitator

2i. Domain Expert Representative

2j. Business Requirements Analyst

2k. Conformance Facilitator

2l. Other Facilitators

2m. Implementers

3a. Project Scope

the encoding rules for HL7 Version 3 messages based on XML (Extensible Markup Language). Several XML encoding methods could serve as a messaging syntax for HL7 V3 messages. This document represents the method that is recommended by HL7, describing the underlying rules and principles. The corresponding data type descriptions necessary for this specification are described in the Data Types XML ITS.

Attachments

3b. Project Need

This is a base specification underlying V3 representation of information models.

3c. Security Risk

No

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

Reaffirmation Ballot May 2023 cycle

3f. Common Names / Keywords / Aliases:

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/documentcenter/private/standards/v3/V3_XMLITS_STRUCT_R2_2018APR.zip

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

3n. List of Vocabularies

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

4a. Products

V3 Messages - Infrastructure

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

6b. Content Already Developed

6c. Content externally developed?

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, Regulatory Agency, Standards Development Organizations (SDOs), Payors

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

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

7j. TSC Approval Date



Version

3

Modifier

Paul Knapp

Modify Date

Jan 17, 2023 19:22

1a. Project Name

Reaffirmation of HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

1b. Project ID

1784

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

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

2a. Primary/Sponsor WG

Financial Management

2d. Project Facilitator

Paul Knapp

2g. Publishing Facilitator

Paul Knapp

3a. Project Scope

the encoding rules for HL7 Version 3 messages based on XML (Extensible Markup Language). Several XML encoding methods could serve as a messaging syntax for HL7 V3 messages. This document represents the method that is recommended by HL7, describing the underlying rules and principles. The corresponding data type descriptions necessary for this specification are described in the Data Types XML ITS.

3b. Project Need

This is a base specification underlying V3 representation of information models.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Reaffirmation Ballot May 2023 cycle

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/documentcenter/private/standards/v3/V3_XMLITS_STRUCT_R2_2018APR.zip

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

V3 Messages - Infrastructure

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

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

No

6f. Stakeholders

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

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

Paul Knapp

Modify Date

Jan 17, 2023 19:18

1a. Project Name

Reaffirmation of HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

1b. Project ID

1784

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

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

2a. Primary/Sponsor WG

Financial Management

2d. Project Facilitator

Paul Knapp

2g. Publishing Facilitator

Paul Knapp

3a. Project Scope

the encoding rules for HL7 Version 3 messages based on XML (Extensible Markup Language). Several XML encoding methods could serve as a messaging syntax for HL7 V3 messages. This document represents the method that is recommended by HL7, describing the underlying rules and principles. The corresponding data type descriptions necessary for this specification are described in the Data Types XML ITS.

3b. Project Need

This is a base specification underlying V3 representation of information models.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Reaffirmation Ballot May 2023 cycle

3i. HL7-Managed Project Document Repository URL:

https://www.hl7.org/login/index.cfm?next=/implement/standards/product_brief.cfm?product_id=304

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

V3 Messages - Infrastructure

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

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

No

6f. Stakeholders

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

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

Paul Knapp

Modify Date

Jan 17, 2023 17:47

1a. Project Name

Reaffirmation of HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

1b. Project ID

1784

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

1f. Name of standard being reaffirmed

HL7 Version 3 Standard: XML Implementation Technology Specification - V3 Structures, Release 2

2a. Primary/Sponsor WG

Financial Management

2d. Project Facilitator

Paul Knapp

2g. Publishing Facilitator

Paul Knapp

3a. Project Scope

the encoding rules for HL7 Version 3 messages based on XML (Extensible Markup Language). Several XML encoding methods could serve as a messaging syntax for HL7 V3 messages. This document represents the method that is recommended by HL7, describing the underlying rules and principles. The corresponding data type descriptions necessary for this specification are described in the Data Types XML ITS.

3b. Project Need

This is a base specification underlying V3 representation of information models.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Reaffirmation Ballot May 2023 cycle

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

V3 Messages - Infrastructure

5a. Project Intent

Reaffirmation of a standard

5b. Project Ballot Type

Normative (no STU)

5d. Joint Copyright

No

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

No

6f. Stakeholders

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

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