Consolidated Conformance Website

1a. Project Name Consolidated Conformance Website 1b. Project ID 1576 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 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 Conformance 2d. Project Facilitator Frank Oemig 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator 2g. Publishing Facilitator 2h. Vocabulary Facilitator 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers 3a. Project Scope The intent of the project is to create a central website that allows for entering the conformance topic/domain at a central location. From there, it should provide a short introduction into the topic and allow by further links to jumo directly to the appropriate locations within the different product lines. Attachments 3b. Project Need URL conformance.hl7.org 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates 3f. Common Names / Keywords / Aliases: 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? No 3l. Reason for not using current V3 data types? 3m. External Vocabularies No 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products Guidance (e.g. Companion Guide, Cookbook, etc) 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 Supplement to a current 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 N/A (project won’t go through ballot) 5c. Additional Ballot Info 5d. Joint Copyright 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? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? 6f. Stakeholders Standards Development Organizations (SDOs) 6f. Other Stakeholders 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 CDA, FHIR, V2 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