hl7.fhir.r3.profiles.resources | CommunicationRequest

Some canonical urls could not be resolved.

You're probably missing a package or made a typo in your canonical.

Could not resolve: http://hl7.org/fhir/StructureDefinition/Identifier
Could not resolve: http://hl7.org/fhir/StructureDefinition/Reference
Could not resolve: http://hl7.org/fhir/StructureDefinition/code
Could not resolve: http://hl7.org/fhir/StructureDefinition/CodeableConcept
Could not resolve: http://hl7.org/fhir/StructureDefinition/BackboneElement
Could not resolve: http://hl7.org/fhir/StructureDefinition/Element
Could not resolve: http://hl7.org/fhir/StructureDefinition/dateTime
Could not resolve: http://hl7.org/fhir/StructureDefinition/Annotation

CommunicationRequest	I		DomainResource	Element id CommunicationRequest Short description A request for information to be sent to a receiver Definition A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition. Data type DomainResource Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative `contained.text.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource `contained.where(('#'+id in %resource.descendants().reference).not()).empty()` Mappings rim: Entity. Role, or Act workflow: Request w5: workflow.order
id	Σ	0..1	id	There are no (further) constraints on this element Element id CommunicationRequest.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type id
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id CommunicationRequest.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. Data type Meta
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id CommunicationRequest.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. Data type uri
language		0..1	codeBinding	There are no (further) constraints on this element Element id CommunicationRequest.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. ?? (extensible)
text	I	0..1	Narrative	There are no (further) constraints on this element Element id CommunicationRequest.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Data type Narrative Mappings rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id CommunicationRequest.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Data type Resource Mappings rim: N/A
extension		0..*	Extension	There are no (further) constraints on this element Element id CommunicationRequest.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: N/A
modifierExtension	?!	0..*	Extension	There are no (further) constraints on this element Element id CommunicationRequest.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id CommunicationRequest.identifier Short description Unique identifier Definition A unique ID of this request for reference purposes. It must be provided if user wants it returned as part of any output, otherwise it will be autogenerated, if needed, by CDS system. Does not need to be the actual ID of the source system. Data type Identifier Mappings workflow: Request.identifier w5: id
basedOn	Σ	0..*	Reference(Resource)	There are no (further) constraints on this element Element id CommunicationRequest.basedOn Short description Fulfills plan or proposal Alternate names fulfills Definition A plan or proposal that is fulfilled in whole or in part by this request. Requirements Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon. Data type Reference(Resource) Mappings workflow: Request.basedOn rim: .outboundRelationship[typeCode=FLFS].target
replaces	Σ	0..*	Reference(CommunicationRequest)	There are no (further) constraints on this element Element id CommunicationRequest.replaces Short description Request(s) replaced by this request Alternate names supersedes, prior Definition Completed or terminated request(s) whose function is taken by this new request. Requirements Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests. Comments The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing. Data type Reference(CommunicationRequest) Mappings workflow: Request.replaces rim: .outboundRelationship[typeCode=RPLC].target
groupIdentifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id CommunicationRequest.groupIdentifier Short description Composite request this is part of Alternate names grouperId Definition A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form. Comments Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation. Data type Identifier Mappings workflow: Request.groupIdentifier rim: .inboundRelationship(typeCode=COMP].source[moodCode=INT].identifier
status	Σ ?!	1..1	codeBinding	There are no (further) constraints on this element Element id CommunicationRequest.status Short description draft \| active \| suspended \| cancelled \| completed \| entered-in-error \| unknown Definition The status of the proposal or order. Comments This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. Data type code Binding The status of the communication request. ?? (required) Mappings workflow: Request.status w5: status
category		0..*	CodeableConcept	There are no (further) constraints on this element Element id CommunicationRequest.category Short description Message category Definition The type of message to be sent such as alert, notification, reminder, instruction, etc. Comments There may be multiple axes of categorization and one communication request may serve multiple purposes. Data type CodeableConcept Binding Codes for general categories of communications such as alerts, instruction, etc. ?? (example) Mappings workflow: Request.code w5: class
priority	Σ	0..1	codeBinding	There are no (further) constraints on this element Element id CommunicationRequest.priority Short description Message urgency Definition Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine. Meaning when missing If missing, this task should be performed with normal priority Data type code Binding Codes indicating the relative importance of a communication request. ?? (required) Mappings workflow: Request.priority w5: grade
medium		0..*	CodeableConcept	There are no (further) constraints on this element Element id CommunicationRequest.medium Short description A channel of communication Definition A channel that was used for this communication (e.g. email, fax). Data type CodeableConcept Binding Codes for communication mediums such as phone, fax, email, in person, etc. ?? (example)
subject		0..1	Reference(Patient \| Group)	There are no (further) constraints on this element Element id CommunicationRequest.subject Short description Focus of message Alternate names patient Definition The patient or group that is the focus of this communication request. Data type Reference(Patient \| Group) Mappings workflow: Request.subject w5: who.focus
recipient		0..*	Reference(Device \| Organization \| Patient \| Practitioner \| RelatedPerson \| Group \| CareTeam)	There are no (further) constraints on this element Element id CommunicationRequest.recipient Short description Message recipient Definition The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication. Data type Reference(Device \| Organization \| Patient \| Practitioner \| RelatedPerson \| Group \| CareTeam) Mappings workflow: Request.performer w5: who.focus
topic		0..*	Reference(Resource)	There are no (further) constraints on this element Element id CommunicationRequest.topic Short description Focal resources Definition The resources which were related to producing this communication request. Data type Reference(Resource) Mappings workflow: Request.supportingInfo w5: context
context	Σ	0..1	Reference(Encounter \| EpisodeOfCare)	There are no (further) constraints on this element Element id CommunicationRequest.context Short description Encounter or episode leading to message Alternate names encounter Definition The encounter or episode of care within which the communication request was created. Data type Reference(Encounter \| EpisodeOfCare) Mappings workflow: Request.context w5: context
payload		0..*	BackboneElement	There are no (further) constraints on this element Element id CommunicationRequest.payload Short description Message payload Definition Text, attachment(s), or resource(s) to be communicated to the recipient. Data type BackboneElement
occurrence[x]	Σ	0..1		There are no (further) constraints on this element Element id CommunicationRequest.occurrence[x] Short description When scheduled Alternate names timing Definition The time when this communication is to occur. Mappings workflow: Request.occurrence w5: when.planned
occurrenceDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
occurrencePeriod			Period	There are no (further) constraints on this element Data type Period
authoredOn	Σ	0..1	dateTime	There are no (further) constraints on this element Element id CommunicationRequest.authoredOn Short description When request transitioned to being actionable Alternate names createdOn Definition For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation. Data type dateTime Mappings workflow: Request.authoredOn w5: when.recorded
sender		0..1	Reference(Device \| Organization \| Patient \| Practitioner \| RelatedPerson)	There are no (further) constraints on this element Element id CommunicationRequest.sender Short description Message sender Definition The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication. Data type Reference(Device \| Organization \| Patient \| Practitioner \| RelatedPerson) Mappings workflow: Request.requester.agent w5: who.actor
requester	Σ I	0..1	BackboneElement	There are no (further) constraints on this element Element id CommunicationRequest.requester Short description Who/what is requesting service Alternate names author Definition The individual who initiated the request and has responsibility for its activation. Data type BackboneElement Constraints cmr-1: onBehalfOf can only be specified if agent is practitioner or device `(agent.resolve() is Practitioner) or (agent.resolve() is Device) or onBehalfOf.exists().not()` Mappings workflow: Request.requester rim: .participation[typeCode=AUT].role
reasonCode	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id CommunicationRequest.reasonCode Short description Why is communication needed? Definition Describes why the request is being made in coded or textual form. Comments Textual reasons can be caprued using reasonCode.text. Data type CodeableConcept Binding Codes for describing reasons for the occurrence of a communication. ?? (example) Mappings workflow: Request.reasonCode rim: .reasonCode w5: why
reasonReference	Σ	0..*	Reference(Condition \| Observation)	There are no (further) constraints on this element Element id CommunicationRequest.reasonReference Short description Why is communication needed? Definition Indicates another resource whose existence justifies this request. Data type Reference(Condition \| Observation) Mappings workflow: Request.reasonReference rim: .outboundRelationship[typeCode=RSON].target w5: why
note		0..*	Annotation	There are no (further) constraints on this element Element id CommunicationRequest.note Short description Comments made about communication request Definition Comments made about the request by the requester, sender, recipient, subject or other participants. Data type Annotation Mappings workflow: Request.note rim: .inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST]

Confirmation

CommunicationRequest

About

Information

Follow us

Links