Repository/Registry Administrator Main contact for the Repository/Registry Interests: Expert in FHIR artifacts and repository/registry processes. Enforces policies, procedures, content documentation and validation requirements. Ensures accurate representation of relationships between artifacts Registry Metadata Annotator/Approver Assists Administrator with FHIR artifact registration and maintenance of status information. Adds / verifies metadata associated with a FHIR artifact to make it more useful to others, e.g. keywords Interests: Administrative workflow and process co-ordination; stakeholder communication and co-ordination; annotating content to enhance its business usefulness FHIR artifact Contributor Organization / Governance Group FHIR artifact Submitter The original submitter of a FHIR artifact to the repository. Interests: Creates and/or submits the FHIR artifact and assumes responsibility for its support FHIR artifact Validator Validates FHIR artifact. use approved validation tools and submits proof of validation (including any errors) FHIR artifact Metadata Submitter Submits metadata associated with the FHIR artifact: creates and maintains FHIR artifact metadata for the lifecycle of the artifact. FHIR artifact Adopter Organization FHIR artifact Adopter Asserts that a specific FHIR artifact is in use within the adopter's organization. Records usage details in the registry. Interests: Sharing implementation experience and contributing to wider knowledge about FHIR artifact’s purpose and utilization. FHIR artifact Repository/Registry Organization FHIR artifact Repository/Registry
Notes for comment: The roles and interests of stakeholders are maintained through a simple FHIR artifacts repository/registry user registration process. All stakeholders, except for FHIR artifacts Information Consumers, will nominate representative user(s) who can maintain repository/registry content on their behalf. The repository/registry can be queried by non-registered users. Who can make changes -- Keep track of pathway -- Track adoption -- author – group - attribution Author / submitter Av0 - Av1 – Av2 (adopted/adapted by OO at Av1 now called OOA V0 (with attribution to Av1) Backward compatible – open – can add if not constrained -- if constrained, need new template ID Artifact may need to be tracked to a “source” repository
Stakeholder Entity : Stakeholder Entity: Interactions Notes: From FHIR Artifacts Registry To FHIR artifacts Custodian Organization Transmits requests from FHIR artifact Information Consumers. Makes available FHIR artifact Adaptations and Adoptions metadata, as well as linking data to Custodian Organization. To FHIR artifact Adopter Organization Acknowledges receipt of Adopter Organization metadata. To FHIR artifact Information Consumer Provides metadata on FHIR artifacts, and responds to user queries. Also may transmit to consumers the FHIR Artifact Custodian Organizations responses to specific user queries.
Balloting and Publication Process The FHIR publication process applies to both publication of the base standard (e..g FHIR STU 3.0 and any balloted FHIR implementation guides. The goal is to create a static view of all FHIR artifacts associated with the ballot for review and comment. The process requires that the specific artifacts stay static (other than changes applied during the comment reconciliation and disposition process) during the entire ballot process. This needs to be done without impacting the ability to continue to evolve the base standard create new implementation guides. Prior to ballot, the system will provide for: Selection and creation of a static version of all artifact that will be balloted together (“ballot contents”) Publishing the ballot contents so HL7 member can review and provide ballot comments during the comment portion of the process. Each item in the ballot contents shall have a unique designation to permit specific comments that clearly identify the particular FHIR artifact and the individual “element” that is the subject of the comment. As part of the comment and comment resolution process Each comment shall be attributed to the comment author and shall be associated, here possible with unique target of the comment. The system shall automatically allow for aggregation of comments by: Author Artifact Type of comment Categories provided for selection as part of the comment process Status (provisional, submitted, in process, withdrawn, disposed, applied, …) The system shall support recording dispositions and pointing directly to their application in the specific FHIR artifacts where possible The authoring system shall be used to apply the updates to the affected FHIR artifacts. (This includes the ability to validate and test as frequently as required) The system shall provide the ability for the comment author (or any other authorized user else) to review the disposition of their / specific comments and trance the result directly to the modified artifact (including documentation).