Clinical Document Architecture V2.0.1
2.1.0 - CI Build
Clinical Document Architecture V2.0.1, published by Health Level 7. This is not an authorized publication; it is the continuous build for version 2.1.0). This version is based on the current content of https://github.com/HL7/cda-core-2.0/ and changes regularly. See the Directory of published versions
Defining URL: | http://hl7.org/fhir/cda/StructureDefinition/RegionOfInterest |
Version: | 2.1.0 |
Name: | CDAR2.RegionOfInterest |
Title: | RegionOfInterest (CDA Class) |
Status: | Active as of 2021-02-19T02:22:17+00:00 |
Definition: | A derivative of the RIM Observation class that represents a region of interest on an image, using an overlay shape. RegionOfInterest is used to make reference to specific regions in images, e.g., to specify the site of a physical finding by "circling" a region in a schematic picture of a human body. The units of the coordinate values in RegionOfInterest.value are in pixels, expressed as a list of integers. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a RegionOfInterest and its referenced ObservationMedia or ExternalObservation is specified by traversing the entryRelationship or reference class, respectively, where typeCode equals "SUBJ". A RegionOfInterest must reference exactly one ObservationMedia or one ExternalObservation. If the RegionOfInterest is the target of a <renderMultimedia> reference, then it shall only reference an ObservationMedia and not an ExternalObservation. An XML attribute "ID" of type XML ID, is added to RegionOfInterest within the CDA Schema. This attribute serves as the target of a renderMultiMedia reference (see renderMultiMedia). All values of attributes of type XML ID must be unique within the document (per the W3C XML specification). |
Publisher: | Health Level 7 |
Source Resource: | XML / JSON / Turtle |
The official URL for this profile is:
http://hl7.org/fhir/cda/StructureDefinition/RegionOfInterest
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from Base
This structure is derived from Base
This structure is derived from Base
Differential View
This structure is derived from Base
Snapshot View
Path | Conformance | ValueSet / Code |
RegionOfInterest.classCode | required | Fixed Value: ROIOVL |
RegionOfInterest.moodCode | required | Fixed Value: EVN |
RegionOfInterest.subject.typeCode | required | Fixed Value: SBJ |
RegionOfInterest.subject.contextControlCode | required | Fixed Value: OP |
RegionOfInterest.subject.awarenessCode | extensible | TargetAwareness |
RegionOfInterest.specimen.typeCode | required | Fixed Value: SPC |
RegionOfInterest.performer.typeCode | required | Fixed Value: PRF |
RegionOfInterest.performer.modeCode | extensible | ParticipationMode |
RegionOfInterest.informant.typeCode | required | Fixed Value: INF |
RegionOfInterest.informant.contextControlCode | required | Fixed Value: OP |
RegionOfInterest.participant.typeCode | required | ParticipationType |
RegionOfInterest.participant.contextControlCode | required | Fixed Value: OP |
RegionOfInterest.participant.awarenessCode | extensible | TargetAwareness |
RegionOfInterest.precondition.typeCode | required | Fixed Value: PRCN |
Id | Path | Details | Requirements |
roi-er-1 | RegionOfInterest.entryRelationship | Only one of observation, regionOfInterest, observationMedia, substanceAdministration, supply, procedure, encounter, organizer, and act : (observation | regionOfInterest | observationMedia | substanceAdministration | supply | procedure | encounter | organizer | act).count() = 1 |