Argo CGM Write, published by Argonaut. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cgm/ and changes regularly. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Resource Profile: Data Submission Standing Order

A base profile for standing orders that indicate data submission requirements. This profile can be used as-is for general data submissions or inherited by more specific data submission profiles.

Key aspects of this profile:

• Specifies what data should be included in each submission
• Defines how often data should be submitted
• Indicates the lookback period each submission should cover

This profile uses the DataSubmissionSchedule extension to capture detailed submission requirements.

Usage:

• Derived from this Resource Profile: CGM Data Submission Standing Order

Formal Views of Profile Content

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

• Differential Table
• Key Elements Table
• Snapshot Table
• Statistics/References
• All

This structure is derived from ServiceRequest

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest		0..*	ServiceRequest	A request for a service to be performed
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
intent		1..1	code	Intent is #order Required Pattern: order
code	S	1..1	CodeableConcept	Code identifying the type of data submission standing order
subject	S	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest	C	0..*	ServiceRequest	A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order.
intent	?!Σ	1..1	code	Intent is #order Binding: RequestIntent (required): The kind of service request. Required Pattern: order
doNotPerform	?!Σ	0..1	boolean	True if service/procedure should not be performed
code	SΣ	1..1	CodeableConcept	Code identifying the type of data submission standing order Binding: ProcedureCodes(SNOMEDCT) (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here.
subject	SΣ	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
ServiceRequest.status	required	RequestStatus http://hl7.org/fhir/ValueSet/request-status|4.0.1 from the FHIR Standard
ServiceRequest.intent	required	Pattern: order http://hl7.org/fhir/ValueSet/request-intent|4.0.1 from the FHIR Standard
ServiceRequest.code	example	ProcedureCodes(SNOMEDCT) http://hl7.org/fhir/ValueSet/procedure-code from the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	ServiceRequest	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	ServiceRequest	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	ServiceRequest	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-5	error	ServiceRequest	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	ServiceRequest	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
prr-1	error	ServiceRequest	orderDetail SHALL only be present if code is present : orderDetail.empty() or code.exists()

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest	C	0..*	ServiceRequest	A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Identifiers assigned to this order
instantiatesCanonical	Σ	0..*	canonical(ActivityDefinition | PlanDefinition)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan | ServiceRequest | MedicationRequest)	What request fulfills
replaces	Σ	0..*	Reference(ServiceRequest)	What request replaces
requisition	Σ	0..1	Identifier	Composite Request ID
status	?!Σ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order.
intent	?!Σ	1..1	code	Intent is #order Binding: RequestIntent (required): The kind of service request. Required Pattern: order
category	Σ	0..*	CodeableConcept	Classification of service Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.
priority	Σ	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.
doNotPerform	?!Σ	0..1	boolean	True if service/procedure should not be performed
code	SΣ	1..1	CodeableConcept	Code identifying the type of data submission standing order Binding: ProcedureCodes(SNOMEDCT) (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here.
orderDetail	ΣC	0..*	CodeableConcept	Additional order information Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.
quantity[x]	Σ	0..1		Service amount
quantityQuantity			Quantity
quantityRatio			Ratio
quantityRange			Range
subject	SΣ	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
encounter	Σ	0..1	Reference(Encounter)	Encounter in which the request was created
occurrence[x]	Σ	0..1		When service should occur
occurrenceDateTime			dateTime
occurrencePeriod			Period
occurrenceTiming			Timing
asNeeded[x]	Σ	0..1		Preconditions for service Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
asNeededBoolean			boolean
asNeededCodeableConcept			CodeableConcept
authoredOn	Σ	0..1	dateTime	Date request signed
requester	Σ	0..1	Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)	Who/what is requesting service
performerType	Σ	0..1	CodeableConcept	Performer role Binding: ParticipantRoles (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
performer	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)	Requested performer
locationCode	Σ	0..*	CodeableConcept	Requested location Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.
locationReference	Σ	0..*	Reference(Location)	Requested location
reasonCode	Σ	0..*	CodeableConcept	Explanation/Justification for procedure or service Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
reasonReference	Σ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Explanation/Justification for service or service
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
supportingInfo		0..*	Reference(Resource)	Additional clinical information
specimen	Σ	0..*	Reference(Specimen)	Procedure Samples
bodySite	Σ	0..*	CodeableConcept	Location on Body Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
note		0..*	Annotation	Comments
patientInstruction	Σ	0..1	string	Patient or consumer-oriented instructions
relevantHistory		0..*	Reference(Provenance)	Request provenance
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
ServiceRequest.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
ServiceRequest.status	required	RequestStatus http://hl7.org/fhir/ValueSet/request-status|4.0.1 from the FHIR Standard
ServiceRequest.intent	required	Pattern: order http://hl7.org/fhir/ValueSet/request-intent|4.0.1 from the FHIR Standard
ServiceRequest.category	example	ServiceRequestCategoryCodes http://hl7.org/fhir/ValueSet/servicerequest-category from the FHIR Standard
ServiceRequest.priority	required	RequestPriority http://hl7.org/fhir/ValueSet/request-priority|4.0.1 from the FHIR Standard
ServiceRequest.code	example	ProcedureCodes(SNOMEDCT) http://hl7.org/fhir/ValueSet/procedure-code from the FHIR Standard
ServiceRequest.orderDetail	example	ServiceRequestOrderDetailsCodes http://hl7.org/fhir/ValueSet/servicerequest-orderdetail from the FHIR Standard
ServiceRequest.asNeeded[x]	example	SNOMEDCTMedicationAsNeededReasonCodes http://hl7.org/fhir/ValueSet/medication-as-needed-reason from the FHIR Standard
ServiceRequest.performerType	example	ParticipantRoles http://hl7.org/fhir/ValueSet/participant-role from the FHIR Standard
ServiceRequest.locationCode	example	ServiceDeliveryLocationRoleType http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
ServiceRequest.reasonCode	example	ProcedureReasonCodes http://hl7.org/fhir/ValueSet/procedure-reason from the FHIR Standard
ServiceRequest.bodySite	example	SNOMEDCTBodyStructures http://hl7.org/fhir/ValueSet/body-site from the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	ServiceRequest	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	ServiceRequest	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	ServiceRequest	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-5	error	ServiceRequest	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	ServiceRequest	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
prr-1	error	ServiceRequest	orderDetail SHALL only be present if code is present : orderDetail.empty() or code.exists()

This structure is derived from ServiceRequest

Summary

Mandatory: 1 element
Must-Support: 2 elements

Extensions

This structure refers to these extensions:

• http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule

Differential View

This structure is derived from ServiceRequest

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest		0..*	ServiceRequest	A request for a service to be performed
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
intent		1..1	code	Intent is #order Required Pattern: order
code	S	1..1	CodeableConcept	Code identifying the type of data submission standing order
subject	S	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
Documentation for this format

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest	C	0..*	ServiceRequest	A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order.
intent	?!Σ	1..1	code	Intent is #order Binding: RequestIntent (required): The kind of service request. Required Pattern: order
doNotPerform	?!Σ	0..1	boolean	True if service/procedure should not be performed
code	SΣ	1..1	CodeableConcept	Code identifying the type of data submission standing order Binding: ProcedureCodes(SNOMEDCT) (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here.
subject	SΣ	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
ServiceRequest.status	required	RequestStatus http://hl7.org/fhir/ValueSet/request-status|4.0.1 from the FHIR Standard
ServiceRequest.intent	required	Pattern: order http://hl7.org/fhir/ValueSet/request-intent|4.0.1 from the FHIR Standard
ServiceRequest.code	example	ProcedureCodes(SNOMEDCT) http://hl7.org/fhir/ValueSet/procedure-code from the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	ServiceRequest	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	ServiceRequest	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	ServiceRequest	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-5	error	ServiceRequest	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	ServiceRequest	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
prr-1	error	ServiceRequest	orderDetail SHALL only be present if code is present : orderDetail.empty() or code.exists()

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
ServiceRequest	C	0..*	ServiceRequest	A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
Slices for extension		0..*	Extension	DataSubmissionSchedule extensions Slice: Unordered, Open by value:url
dataSubmissionSchedule		0..*	(Complex)	Schedules for data submission URL: http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Identifiers assigned to this order
instantiatesCanonical	Σ	0..*	canonical(ActivityDefinition | PlanDefinition)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan | ServiceRequest | MedicationRequest)	What request fulfills
replaces	Σ	0..*	Reference(ServiceRequest)	What request replaces
requisition	Σ	0..1	Identifier	Composite Request ID
status	?!Σ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order.
intent	?!Σ	1..1	code	Intent is #order Binding: RequestIntent (required): The kind of service request. Required Pattern: order
category	Σ	0..*	CodeableConcept	Classification of service Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.
priority	Σ	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.
doNotPerform	?!Σ	0..1	boolean	True if service/procedure should not be performed
code	SΣ	1..1	CodeableConcept	Code identifying the type of data submission standing order Binding: ProcedureCodes(SNOMEDCT) (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here.
orderDetail	ΣC	0..*	CodeableConcept	Additional order information Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.
quantity[x]	Σ	0..1		Service amount
quantityQuantity			Quantity
quantityRatio			Ratio
quantityRange			Range
subject	SΣ	1..1	Reference(Patient | Group | Location | Device)	Patient for the submission order
encounter	Σ	0..1	Reference(Encounter)	Encounter in which the request was created
occurrence[x]	Σ	0..1		When service should occur
occurrenceDateTime			dateTime
occurrencePeriod			Period
occurrenceTiming			Timing
asNeeded[x]	Σ	0..1		Preconditions for service Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
asNeededBoolean			boolean
asNeededCodeableConcept			CodeableConcept
authoredOn	Σ	0..1	dateTime	Date request signed
requester	Σ	0..1	Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)	Who/what is requesting service
performerType	Σ	0..1	CodeableConcept	Performer role Binding: ParticipantRoles (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
performer	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)	Requested performer
locationCode	Σ	0..*	CodeableConcept	Requested location Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.
locationReference	Σ	0..*	Reference(Location)	Requested location
reasonCode	Σ	0..*	CodeableConcept	Explanation/Justification for procedure or service Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
reasonReference	Σ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Explanation/Justification for service or service
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
supportingInfo		0..*	Reference(Resource)	Additional clinical information
specimen	Σ	0..*	Reference(Specimen)	Procedure Samples
bodySite	Σ	0..*	CodeableConcept	Location on Body Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
note		0..*	Annotation	Comments
patientInstruction	Σ	0..1	string	Patient or consumer-oriented instructions
relevantHistory		0..*	Reference(Provenance)	Request provenance
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
ServiceRequest.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
ServiceRequest.status	required	RequestStatus http://hl7.org/fhir/ValueSet/request-status|4.0.1 from the FHIR Standard
ServiceRequest.intent	required	Pattern: order http://hl7.org/fhir/ValueSet/request-intent|4.0.1 from the FHIR Standard
ServiceRequest.category	example	ServiceRequestCategoryCodes http://hl7.org/fhir/ValueSet/servicerequest-category from the FHIR Standard
ServiceRequest.priority	required	RequestPriority http://hl7.org/fhir/ValueSet/request-priority|4.0.1 from the FHIR Standard
ServiceRequest.code	example	ProcedureCodes(SNOMEDCT) http://hl7.org/fhir/ValueSet/procedure-code from the FHIR Standard
ServiceRequest.orderDetail	example	ServiceRequestOrderDetailsCodes http://hl7.org/fhir/ValueSet/servicerequest-orderdetail from the FHIR Standard
ServiceRequest.asNeeded[x]	example	SNOMEDCTMedicationAsNeededReasonCodes http://hl7.org/fhir/ValueSet/medication-as-needed-reason from the FHIR Standard
ServiceRequest.performerType	example	ParticipantRoles http://hl7.org/fhir/ValueSet/participant-role from the FHIR Standard
ServiceRequest.locationCode	example	ServiceDeliveryLocationRoleType http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
ServiceRequest.reasonCode	example	ProcedureReasonCodes http://hl7.org/fhir/ValueSet/procedure-reason from the FHIR Standard
ServiceRequest.bodySite	example	SNOMEDCTBodyStructures http://hl7.org/fhir/ValueSet/body-site from the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	ServiceRequest	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	ServiceRequest	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	ServiceRequest	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-5	error	ServiceRequest	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	ServiceRequest	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
prr-1	error	ServiceRequest	orderDetail SHALL only be present if code is present : orderDetail.empty() or code.exists()

This structure is derived from ServiceRequest

Summary

Mandatory: 1 element
Must-Support: 2 elements

Extensions

This structure refers to these extensions:

• http://hl7.org/uv/cgm/StructureDefinition/data-submission-schedule

Other representations of profile: CSV, Excel, Schematron