Change record: HL7 publishes updated CRD, DTR, and PAS implementation guides
HL7 published CRD 2.2.1, DTR 2.2.0, and PAS 2.2.1 as coordinated Standard for Trial Use releases.
What changed
HL7 published CRD 2.2.1, DTR 2.2.0, and PAS 2.2.1 as coordinated Standard for Trial Use releases.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
Vendor and payer conformance claims should identify the exact guide, version, workflow stage, test evidence, and production counterparty coverage.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Authorization Requirement Discovery
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for authorization requirement discovery.
Clinical Documentation Assembly
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for clinical documentation assembly.
Medical-Service Electronic Submission
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for medical-service electronic submission.
FHIR CRD, DTR, And PAS Interoperability
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for FHIR CRD, DTR, and PAS interoperability.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Official standards publication. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.