DSTU2 QA Preview

This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

6.8.12.3 StructureDefinition: MeasureReport

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/measurereport

A set of resources composed into a single coherent clinical statement with clinical attestation

This profile was published on Fri, Jan 31, 2014 00:00+1100 as a draft by Health Level Seven, Inc. - Clinical Quality Information WG.

6.8.12.3.1 Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Composition.

Summary

Mandatory: 7 elements (+2 nested mandatory elements)
Must-Support: 5 elements
Prohibited: 5 elements

This structure is derived from Composition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*CompositionA set of resources composed into a single coherent clinical statement with clinical attestation
... identifier 0..1IdentifierLogical identifier of composition (version-independent)
... date 1..1dateTimeComposition editing time
... type 1..1CodeableConceptKind of composition (LOINC if possible)
... class 0..1CodeableConceptCategorization of Composition
... title 1..1stringHuman Readable name/title
... status 1..1codepreliminary | final | appended | amended | entered-in-error
... confidentiality 1..1codeAs defined by affinity domain
... subject 1..1Reference(Patient | Practitioner | Group | Device | Location)Who and/or what the composition is about
... author 1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester 0..*BackboneElementAttests to accuracy of composition
.... mode 1..*codepersonal | professional | legal | official
.... time 0..1dateTimeWhen composition attested
.... party 0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian 0..1Reference(Organization)Org which maintains the composition
... event S0..0
... encounter S0..0
... section 0..*BackboneElementComposition is broken into sections
.... title 0..1stringLabel for section
.... entry 1..1Reference(Observation)The Content of the section

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*CompositionA set of resources composed into a single coherent clinical statement with clinical attestation
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..1IdentifierLogical identifier of composition (version-independent)
... date ∑1..1dateTimeComposition editing time
... type ∑1..1CodeableConceptKind of composition (LOINC if possible)
Binding: FHIR Document Type Codes (preferred)
... class ∑0..1CodeableConceptCategorization of Composition
Binding: FHIR Document Class Codes (example)
... title ∑1..1stringHuman Readable name/title
... status ?! ∑1..1codepreliminary | final | appended | amended | entered-in-error
Binding: CompositionStatus (required)
... confidentiality ?! ∑1..1codeAs defined by affinity domain
Binding: v3 Code System Confidentiality (required)
... subject ∑1..1Reference(Patient | Practitioner | Group | Device | Location)Who and/or what the composition is about
... author ∑1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester ∑0..*BackboneElementAttests to accuracy of composition
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... mode ∑1..*codepersonal | professional | legal | official
Binding: CompositionAttestationMode (required)
.... time ∑0..1dateTimeWhen composition attested
.... party ∑0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian ∑0..1Reference(Organization)Org which maintains the composition
... section I0..*BackboneElementComposition is broken into sections
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... title 0..1stringLabel for section
.... code 0..1CodeableConceptClassification of section (recommended)
Binding: Document Section Codes (example)
.... text I0..1NarrativeText summary of the section, for human interpretation
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptWhat order the section entries are in
Binding: List Order Codes (preferred)
.... entry I1..1Reference(Observation)The Content of the section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Nested Section

doco Documentation for this format

todo

This structure is derived from Composition.

Summary

Mandatory: 7 elements (+2 nested mandatory elements)
Must-Support: 5 elements
Prohibited: 5 elements

Differential View

This structure is derived from Composition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*CompositionA set of resources composed into a single coherent clinical statement with clinical attestation
... identifier 0..1IdentifierLogical identifier of composition (version-independent)
... date 1..1dateTimeComposition editing time
... type 1..1CodeableConceptKind of composition (LOINC if possible)
... class 0..1CodeableConceptCategorization of Composition
... title 1..1stringHuman Readable name/title
... status 1..1codepreliminary | final | appended | amended | entered-in-error
... confidentiality 1..1codeAs defined by affinity domain
... subject 1..1Reference(Patient | Practitioner | Group | Device | Location)Who and/or what the composition is about
... author 1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester 0..*BackboneElementAttests to accuracy of composition
.... mode 1..*codepersonal | professional | legal | official
.... time 0..1dateTimeWhen composition attested
.... party 0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian 0..1Reference(Organization)Org which maintains the composition
... event S0..0
... encounter S0..0
... section 0..*BackboneElementComposition is broken into sections
.... title 0..1stringLabel for section
.... entry 1..1Reference(Observation)The Content of the section

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*CompositionA set of resources composed into a single coherent clinical statement with clinical attestation
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..1IdentifierLogical identifier of composition (version-independent)
... date ∑1..1dateTimeComposition editing time
... type ∑1..1CodeableConceptKind of composition (LOINC if possible)
Binding: FHIR Document Type Codes (preferred)
... class ∑0..1CodeableConceptCategorization of Composition
Binding: FHIR Document Class Codes (example)
... title ∑1..1stringHuman Readable name/title
... status ?! ∑1..1codepreliminary | final | appended | amended | entered-in-error
Binding: CompositionStatus (required)
... confidentiality ?! ∑1..1codeAs defined by affinity domain
Binding: v3 Code System Confidentiality (required)
... subject ∑1..1Reference(Patient | Practitioner | Group | Device | Location)Who and/or what the composition is about
... author ∑1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester ∑0..*BackboneElementAttests to accuracy of composition
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... mode ∑1..*codepersonal | professional | legal | official
Binding: CompositionAttestationMode (required)
.... time ∑0..1dateTimeWhen composition attested
.... party ∑0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian ∑0..1Reference(Organization)Org which maintains the composition
... section I0..*BackboneElementComposition is broken into sections
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... title 0..1stringLabel for section
.... code 0..1CodeableConceptClassification of section (recommended)
Binding: Document Section Codes (example)
.... text I0..1NarrativeText summary of the section, for human interpretation
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptWhat order the section entries are in
Binding: List Order Codes (preferred)
.... entry I1..1Reference(Observation)The Content of the section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Nested Section

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

6.8.12.3.2 Terminology Bindings

PathNameConformanceValueSet
Composition.language?extrequiredhttp://tools.ietf.org/html/bcp47
Composition.typeFHIR Document Type CodespreferredFHIR Document Type Codes
Composition.classFHIR Document Class CodesexampleFHIR Document Class Codes
Composition.statusCompositionStatusrequiredCompositionStatus
Composition.confidentialityv3 Code System Confidentialityrequiredv3 Code System Confidentiality
Composition.attester.modeCompositionAttestationModerequiredCompositionAttestationMode
Composition.section.codeDocument Section CodesexampleDocument Section Codes
Composition.section.modeListModerequiredListMode
Composition.section.orderedByList Order CodespreferredList Order Codes
Composition.section.emptyReasonList Empty ReasonspreferredList Empty Reasons

6.8.12.3.3 Constraints

IdPathDetailsRequirements
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
.