Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest vs http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-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	2022-10-07	2023-06-25T16:57:50+00:00	Values Differ
description	This profile sets minimum expectations for recording, searching, and fetching the ServiceRequest resource to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.	This resource is used to "order" services (e.g. non-DME (device) and non-medications). For this version of the IG, it is used primarily to order Home Health Services.	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreServiceRequestProfile	PAOxServiceRequest	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7	Values Differ
purpose		Purpose	Added the item 'Purpose'
status	active
title	US Core ServiceRequest Profile	PAO ServiceRequest	Values Differ
type	ServiceRequest
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest	http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-servicerequest	Values Differ
version	6.1.0-snapshot1	0.2.2	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
ServiceRequest	C	0..*	ServiceRequest	A request for a service to be performed	C	0..*	ServiceRequest	A request for a service to be performed	Elements differ in definition: '\-' vs 'A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.'
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	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: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
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	Additional content defined by implementations
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	Σ	0..*	Reference(CarePlan | ServiceRequest | MedicationRequest)	What request fulfills
replaces	Σ	0..*	Reference(ServiceRequest)	What request replaces	SΣ	0..*	Reference(PAO ServiceRequest)	What request replaces	Elements differ in definition for mustSupport: 'false' vs 'true'
requisition	Σ	0..1	Identifier	Composite Request ID	Σ	0..1	Identifier	Composite Request ID
status	?!SΣ	1..1	code	(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order.	?!SΣ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order.	Elements differ in short: '(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown' vs 'draft | active | on-hold | revoked | completed | entered-in-error | unknown'
intent	?!SΣ	1..1	code	(USCDI) proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request.	?!SΣ	1..1	code	proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. Fixed Value: order	Elements differ in short: '(USCDI) proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option' vs 'proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option'
Slices for category	SΣ	0..*	CodeableConcept	(USCDI) Classification of service Slice: Unordered, Open by pattern:$this Binding: ?? (example): Classification of the requested service.	SΣ	0..*	CodeableConcept	Classification of service Binding: ?? (example): Classification of the requested service.	Elements differ in short: '(USCDI) Classification of service' vs 'Classification of service'
priority	Σ	0..1	code	routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.	SΣ	0..1	code	routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.	Elements differ in definition for mustSupport: 'false' vs 'true'
doNotPerform	?!Σ	0..1	boolean	True if service/procedure should not be performed	?!Σ	0..1	boolean	True if service/procedure should not be performed
code	SΣ	1..1	CodeableConcept	(USCDI) What is being requested/ordered Binding: ?? (extensible)	SΣ	0..1	CodeableConcept	What is being requested/ordered Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred and a valueset using LOINC Order codes is available here.	Elements differ in short: '(USCDI) What is being requested/ordered' vs 'What is being requested/ordered' Element minimum cardinalities differ: '1' vs '0'
orderDetail	ΣC	0..*	CodeableConcept	Additional order information Binding: ?? (example): Codified order entry details which are based on order context.	SΣC	0..*	CodeableConcept	Additional order information Binding: ?? (example): Codified order entry details which are based on order context.	Elements differ in definition for mustSupport: 'false' vs 'true'
quantity[x]	Σ	0..1	Quantity, Ratio, Range	Service amount	Σ	0..1	Quantity, Ratio, Range	Service amount
subject	SΣ	1..1	Reference(US Core Patient Profile)	(USCDI) Individual or Entity the service is ordered for	SΣ	1..1	Reference(US Core Patient Profile)	Individual or Entity the service is ordered for	Elements differ in short: '(USCDI) Individual or Entity the service is ordered for' vs 'Individual or Entity the service is ordered for'
encounter	Σ	0..1	Reference(Encounter)	Encounter in which the request was created	SΣ	0..1	Reference(US Core Encounter Profile)	Encounter in which the request was created	Elements differ in definition for mustSupport: 'false' vs 'true'
occurrence[x]	SΣ	0..1	Period S, dateTime, Timing	(USCDI) When service should occur	SΣ	0..1	dateTime, Period, Timing	When service should occur	Elements differ in short: '(USCDI) When service should occur' vs 'When service should occur'
asNeeded[x]	Σ	0..1	boolean, CodeableConcept	Preconditions for service Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.	SΣ	0..1	boolean, CodeableConcept	Preconditions for service Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.	Elements differ in definition for mustSupport: 'false' vs 'true'
authoredOn	SΣ	0..1	dateTime	(USCDI) Date request signed	SΣ	1..1	dateTime	Date request signed	Elements differ in short: '(USCDI) Date request signed' vs '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 RelatedPerson Profile | Device)	(USCDI) Who/what is requesting service	SΣ	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Who/what is requesting service	Elements differ in short: '(USCDI) Who/what is requesting service' vs 'Who/what is requesting service' Element minimum cardinalities differ: '0' vs '1'
performerType	Σ	0..1	CodeableConcept	Performer role Binding: ?? (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: ?? (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	Σ	0..*	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile | US Core CareTeam Profile)	Requested performer
locationCode	Σ	0..*	CodeableConcept	Requested location Binding: ?? (example): A location type where services are delivered.	SΣ	0..*	CodeableConcept	Requested location Binding: ?? (example): A location type where services are delivered.	Elements differ in definition for mustSupport: 'false' vs 'true'
locationReference	Σ	0..*	Reference(Location)	Requested location	Σ	0..*	Reference(US Core Location Profile)	Requested location
reasonCode	Σ	0..*	CodeableConcept	(USCDI) Explanation/Justification for procedure or service Binding: ?? (extensible)	SΣ	0..*	CodeableConcept	Explanation/Justification for procedure or service Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.	Elements differ in short: '(USCDI) Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service' Elements differ in definition for mustSupport: 'false' vs 'true'
reasonReference	Σ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	(USCDI) US Core Profile that supports the requested service	SΣ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Explanation/Justification for service or service	Elements differ in short: '(USCDI) US Core Profile that supports the requested service' vs 'Explanation/Justification for service or service' Elements differ in definition for mustSupport: 'false' vs 'true'
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage	S	0..*	Reference(PAO Coverage)	Associated insurance coverage	Elements differ in definition for mustSupport: 'false' vs 'true'
supportingInfo		0..*	Reference(Resource)	Additional clinical information	S	0..*	Reference(Resource)	Additional clinical information	Elements differ in definition for mustSupport: 'false' vs 'true'
specimen	Σ	0..*	Reference(Specimen)	Procedure Samples	Σ	0..*	Reference(Specimen)	Procedure Samples
bodySite	Σ	0..*	CodeableConcept	Location on Body Binding: ?? (example): Codes describing anatomical locations. May include laterality.	SΣ	0..*	CodeableConcept	Location on Body Binding: ?? (example): Codes describing anatomical locations. May include laterality.	Elements differ in definition for mustSupport: 'false' vs 'true'
note		0..*	Annotation	Comments	S	0..*	Annotation	Comments	Elements differ in definition for mustSupport: 'false' vs 'true'
patientInstruction	Σ	0..1	string	Patient or consumer-oriented instructions	SΣ	0..1	string	Patient or consumer-oriented instructions	Elements differ in definition for mustSupport: 'false' vs 'true'
relevantHistory		0..*	Reference(Provenance)	Request provenance	S	0..*	Reference(PAO Provenance)	Request provenance	Elements differ in definition for mustSupport: 'false' vs 'true'
Documentation for this format