Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest vs http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/ServiceRequest
copyright	Used by permission of HL7 International, all rights reserved Creative Commons License		Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
date	2018-08-22T00:00:00+00:00	2018-07-25	Values Differ
description	Defines constraints and extensions on the ServiceRequest resource for the minimal set of data to query and retrieve orders associated with diagnostic and clinical tests and clinical interventions for a patient	This profile specifies constraints on the ServiceRequest resource to support coverage requirements discovery.	Values Differ
experimental		false	Added the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreServiceRequest	ServiceRequest	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 International - Financial Management Work Group	Values Differ
purpose
status	active	draft	Values Differ
title	US Core Service Request		Removed the item 'US Core Service Request'
type	ServiceRequest
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest	http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest	Values Differ
version	4.1.0	1.1.0-ballot	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
ServiceRequest	I	0..*	ServiceRequest	A request for a service to be performed	I	0..*	ServiceRequest	A request for a service to be performed
id	Σ	0..1	string	Logical id of this artifact	Σ	0..1	string	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	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) Max Binding: AllLanguages: A human language.		0..1	code	Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language.
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Extension Slice: Unordered, Open by value:url	Elements differ in short: 'Additional content defined by implementations' vs 'Extension' Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Identifiers assigned to this order	SΣ	0..*	Identifier	Identifiers assigned to this order	Elements differ in definition for mustSupport: 'false' vs 'true'
instantiatesCanonical	Σ	0..*	canonical(ActivityDefinition | PlanDefinition)	Instantiates FHIR protocol or definition	Σ	0..*	canonical(ActivityDefinition | PlanDefinition)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan | ServiceRequest | MedicationRequest)	What request fulfills	SΣ	0..*	Reference(ServiceRequest | MedicationRequest)	What request fulfills	Elements differ in definition for mustSupport: 'false' vs 'true' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest], CanonicalType[http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-medicationrequest]])
replaces	Σ	0..*	Reference(ServiceRequest)	What request replaces	Σ	0..*	Reference(ServiceRequest)	What request replaces
requisition	Σ	0..1	Identifier	Composite Request ID	Σ	0..1	Identifier	Composite Request ID
status	?!SΣ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order.	?!SΣ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: RequestStatus (required): The status of a service order. Fixed Value: draft
intent	?!SΣ	1..1	code	proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: RequestIntent (required): The kind of service request.	?!Σ	1..1	code	proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: RequestIntent (required): The kind of service request.	Elements differ in definition for mustSupport: 'true' vs 'false'
Slices for category	SΣ	1..*	CodeableConcept	Classification of service Slice: Unordered, Open by pattern:$this Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.	Σ	0..*	CodeableConcept	Classification of service Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.	Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
priority	Σ	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.	Σ	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	?!Σ	0..0			Element maximum cardinalities differ: '1' vs '0'
code	SΣ	1..1	CodeableConcept	What is being requested/ordered Binding: US Core Procedure Codes (extensible)	SΣ	1..1	CodeableConcept	Codes to identify requested services. (CPT, SNOMED CT or LOINC) Binding: CRD Service Request Codes (extensible): Codes describing the type of Service	Elements differ in short: 'What is being requested/ordered' vs 'Codes to identify requested services. (CPT, SNOMED CT or LOINC)'
orderDetail	ΣI	0..*	CodeableConcept	Additional order information Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.	ΣI	0..*	CodeableConcept	Additional order information Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.
quantity[x]	Σ	0..1	Quantity, Ratio, Range	Service amount	SΣ	0..1	Quantity, Ratio, Range	Service amount	Elements differ in definition for mustSupport: 'false' vs 'true'
subject	SΣ	1..1	Reference(US Core Patient Profile)	Individual or Entity the service is ordered for	SΣ	1..1	Reference(Patient)	Individual or Entity the service is ordered for
encounter	Σ	0..1	Reference(Encounter)	Encounter in which the request was created	Σ	0..1	Reference(Encounter)	Encounter in which the request was created
occurrence[x]	SΣ	0..1	dateTime S, Period, Timing	When service should occur	SΣ	0..1	dateTime, Period, Timing	When service should occur
asNeeded[x]	Σ	0..1	boolean, CodeableConcept	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.	Σ	0..1	boolean, CodeableConcept	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.
authoredOn	SΣ	0..1	dateTime	Date request signed	SΣ	1..1	dateTime	Date request signed	Element minimum cardinalities differ: '0' vs '1'
requester	SΣ	0..1	Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core Related Person | Device)	Who/what is requesting service	SΣ	1..1	Reference(Practitioner | US Core PractitionerRole Profile)	Who/what is requesting service	Element minimum cardinalities differ: '0' vs '1'
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.	Σ	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	SΣ	0..*	Reference(Practitioner | US Core PractitionerRole Profile)	Requested performer	Elements differ in definition for mustSupport: 'false' vs 'true'
locationCode	Σ	0..*	CodeableConcept	Requested location Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.	Σ	0..*	CodeableConcept	Requested location Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.
locationReference	Σ	0..*	Reference(Location)	Requested location	SΣ	1..1	Reference(Location)	Requested location	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1' Element maximum cardinalities differ: '2147483647' vs '1'
reasonCode	Σ	0..*	CodeableConcept	Explanation/Justification for procedure or service Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.	SΣ	0..*	CodeableConcept	Explanation/Justification for procedure or service Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.	Elements differ in definition for mustSupport: 'false' vs 'true'
reasonReference	Σ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Explanation/Justification for service or service	SΣ	0..*	Reference(US Core Condition Profile | US Core Laboratory Result Observation Profile)	Explanation/Justification for service or service	Elements differ in comments: 'This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise when referencing *DiagnosticReport* it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example].' vs 'potentially relevant for CRD in some situations.' Elements differ in definition for mustSupport: 'false' vs 'true'
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
supportingInfo		0..*	Reference(Resource)	Additional clinical information		0..*	Reference(Resource)	Additional clinical information
specimen	Σ	0..*	Reference(Specimen)	Procedure Samples	Σ	0..*	Reference(Specimen)	Procedure Samples
bodySite	Σ	0..*	CodeableConcept	Location on Body Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.	Σ	0..*	CodeableConcept	Location on Body Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
note		0..*	Annotation	Comments		0..*	Annotation	Comments
patientInstruction	Σ	0..1	string	Patient or consumer-oriented instructions	Σ	0..1	string	Patient or consumer-oriented instructions
relevantHistory		0..*	Reference(Provenance)	Request provenance		0..*	Reference(Provenance)	Request provenance
Documentation for this format