Implementation Guidance > Implementation Considerations
Implementation Considerations
The Surgical Efficiency Reporting Information System data standardization guide is the primary source for the content of the individual data elements that comprise the SERIS submissions.
Conformance Rules
FHIR is a general purpose specification and imposes no particular requirements on implementers to support specific resources, operations, search parameters or other capabilities. To achieve interoperability in a particular domain, it's important that implementors make similar decisions about what FHIR capabilities those systems will support. FHIR uses the CapabilityStatement resource to define the actual or expected capabilities of a particular system.
MustSupport Flag
To maximize interoperability, this implementation guide uses the MustSupport flag to identify elements that implementers must understand in order to properly submit, process, or view. Please refer to the guidance below:
Submitting OR Schedules
When submitting an OR Schedule, a system must demonstrate that it is capable of providing the elements marked with the "MustSupport" flag in accordance with the profile definition and associated business rules. OR Schedule submissions may not always contain these elements.
Elements without the "MustSupport" flag in a FHIR data submission may be ignored by the SERIS Repository. No error will be generated because these elements are present or missing.
Submitting OR Case Scheduling/Updating
When submitting an OR Case Scheduling/Update/Completion/Cancel, a system must demonstrate that it is capable of providing the elements marked with the "MustSupport" flag in accordance with the profile definition and associated business rules. OR Case submissions may not always contain these elements.
Elements without the "MustSupport" flag in a FHIR data submission may be ignored by the SERIS Repository. No error will be generated because these elements are present or missing.
Data Formatting
Date
In this specification, the expected date format is "YYYY-MM-DD" in UTC format. If this format is not provided, or an invalid date is provided in the defined format, the request will be rejected. These date and datetime format may be different than the format specified in the Surgical Efficiency Targets Program Data Standardization Guide. Below are the formats supported:
DateTime (accept two formats)
- 2015-01-07T13:28:17-05:00 or
- 2015-01-07T18:28:17Z
URI/UUID
Uniform Resource Identifiers (URIs) leveraged in the SERIS Repository are case sensitive. URIs can be absolute or relative, and may have an optional fragment identifier. Universally Unique IDs (UUIDs) are defined in lower case format (e.g. “urn:uuid:53fefa32-fcbb-4ff8-8a92-55ee120877b7”).