Skip to end of metadata
Go to start of metadata





1a. Project Name

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

1b. Project ID

1562

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

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

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

Infrastructure & Messaging

2d. Project Facilitator

Anthony Julian

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

Anthony Julian

2g. Publishing Facilitator

Anthony Julian

2h. Vocabulary Facilitator

Sandy Stuart

2i. Domain Expert Representative

2j. Business Requirements Analyst

2k. Conformance Facilitator

2l. Other Facilitators

2m. Implementers

3a. Project Scope

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in 2020

Attachments

3b. Project Need

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in /2020

3c. Security Risk

No

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

Submit for ReAffirmation Ballot 2020 May WGM
Complete Normative Reconciliation 2020 Sept WGM
Submit Publication Request 2020 Sept WGM
Receive ANSI Approval 2020 Oct
Project End Date (all objectives have been met) 2020 Oct

3f. Common Names / Keywords / Aliases:

Shared Messages, R3

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

http://wiki.hl7.org/index.php?title=SharedMessageR3-reaff

3j. Backwards Compatibility

N/A

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

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

N/A

6b. Content Already Developed

N/A

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

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

No

6f. Stakeholders

Other

6f. Other Stakeholders

HL7 Standards Developers

6g. Vendors

6g. Other Vendors

6h. Providers

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

7b. Sponsoring WG Approval Date

Oct 10, 2019

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



 Show Changes

Version

2

Modifier

Anthony Julian

Modify Date

Oct 10, 2019 20:12

1a. Project Name

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

1b. Project ID

1562

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

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

2a. Primary/Sponsor WG

Infrastructure & Messaging

2d. Project Facilitator

Anthony Julian

2f. Modeling Facilitator

Anthony Julian

2g. Publishing Facilitator

Anthony Julian

2h. Vocabulary Facilitator

Sandy Stuart

3a. Project Scope

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in 2020

3b. Project Need

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in /2020

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Submit for ReAffirmation Ballot 2020 May WGM
Complete Normative Reconciliation 2020 Sept WGM
Submit Publication Request 2020 Sept WGM
Receive ANSI Approval 2020 Oct
Project End Date (all objectives have been met) 2020 Oct

3f. Common Names / Keywords / Aliases:

Shared Messages, R3

3i. HL7-Managed Project Document Repository URL:

http://wiki.hl7.org/index.php?title=SharedMessageR3-reaff

3j. Backwards Compatibility

N/A

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

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

6a. External Project Collaboration

N/A

6b. Content Already Developed

N/A

6c. Content externally developed?

No

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

No

6f. Stakeholders

Other

6f. Other Stakeholders

HL7 Standards Developers

6i. Realm

Universal

7b. Sponsoring WG Approval Date

Oct 10, 2019

Version

1

Modifier

Anthony Julian

Modify Date

Sep 24, 2019 22:10

1a. Project Name

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

1b. Project ID

1562

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

Reaffirmation of HL7 Version 3 Standard: Shared Messages, Release 3

2a. Primary/Sponsor WG

Infrastructure & Messaging

2d. Project Facilitator

Anthony Julian

2f. Modeling Facilitator

Anthony Julian

2g. Publishing Facilitator

Anthony Julian

2h. Vocabulary Facilitator

Sandy Stuart

3a. Project Scope

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in 2020

3b. Project Need

Reaffirmation of normative standard for HL7 Version 3 Standard: Shared Messages, Release 3. This standard reaches its 5-year ANSI anniversary in /2020

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Submit for ReAffirmation Ballot 2020 May WGM
Complete Normative Reconciliation 2020 Sept WGM
Submit Publication Request 2020 Sept WGM
Receive ANSI Approval 2020 Oct
Project End Date (all objectives have been met) 2020 Oct

3f. Common Names / Keywords / Aliases:

Shared Messages, R3

3i. HL7-Managed Project Document Repository URL:

http://wiki.hl7.org/index.php?title=SharedMessageR3-reaff

3j. Backwards Compatibility

N/A

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

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

6a. External Project Collaboration

N/A

6b. Content Already Developed

N/A

6c. Content externally developed?

No

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

No

6f. Stakeholders

Other

6f. Other Stakeholders

HL7 Standards Developers

6i. Realm

Universal