×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 

Schematron Design and Development for StructureDefinition

Basics

Schematron Design and Development for StructureDefinition

1883
Vendor Contract




Details

Scope of Work:

a. Map StructureDefinitions to Schematron Rules:

Map the elements and constraints defined in the StructureDefinitions to Schematron rules. Each constraint in the StructureDefinition should have a corresponding validation rule in the Schematron.

b. Implement Schematron Rules:

Write the Schematron rules based on the mappings from the StructureDefinitions. These rules should check for compliance with the constraints specified in the StructureDefinitions.

c. Test and Validate:

Test the FHIR StructureDefinition-linked CDA Schematron against a variety of CDA documents to ensure that it accurately validates the required elements and constraints. Adjust as needed.

d. Documentation:

Document the FHIR StructureDefinition-linked CDA Schematron, including the approach taken to mappings between StructureDefinitions and Schematron rules, how to use the validation tool, and any other relevant information.




Scope of Work: a. Map StructureDefinitions to Schematron Rules: Map the elements and constraints defined in the StructureDefinitions to Schematron rules. Each constraint in the StructureDefinition should have a corresponding validation rule in the Schematron. b. Implement Schematron Rules: Write the Schematron rules based on the mappings from the StructureDefinitions. These rules should check for compliance with the constraints specified in the StructureDefinitions. c. Test and Validate: Test the FHIR StructureDefinition-linked CDA Schematron against a variety of CDA documents to ensure that it accurately validates the required elements and constraints. Adjust as needed. d. Documentation: Document the FHIR StructureDefinition-linked CDA Schematron, including the approach taken to mappings between StructureDefinitions and Schematron rules, how to use the validation tool, and any other










N/A

N/A

No

Contract Start Date: April 16, 2024 Contract End Date: July 31, 2024 Contractor Contact Information: Benjamin Flessner (b dot d dot flessner at gmail dot com)
Organization & Realm

Universal

People

Ben Flessner



Board of Directors Work Group


Status & Dates

Active

Active Project (Resources assigned to pjt)

04/19/2024

09/01/2024

2024 Sept WGM/Ballot

09/01/2024

2024 Sept WGM/Ballot

Approvals



Not Needed


Not Needed




System Info