This version of the PS-CA Implementation Guide has been superseded by a newer version. Other releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.


MedicationRequest (PS-CA)

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at Medication Request (PS-CA)

Profile

identifier0..*Identifier
statusS Σ ?!1..1codeBinding
statusReason0..1CodeableConcept
intentΣ ?!1..1codeBinding
category0..*CodeableConcept
priorityΣ0..1codeBinding
doNotPerformΣ ?!0..1boolean
reportedBooleanboolean
reportedReferenceReference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
medicationReferenceS Σ0..1Reference(Medication (PS-CA))
medicationCodeableConceptS Σ0..1Data Type: Codeable Concept (PS-CA)
referenceS Σ I1..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
encounterI0..1Reference(Encounter)
supportingInformationI0..*Reference(Resource)
authoredOnS Σ0..1dateTime
requesterΣ I0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)
performerI0..1Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam)
performerTypeΣ0..1CodeableConcept
recorderI0..1Reference(Practitioner | PractitionerRole)
reasonCode0..*CodeableConcept
reasonReferenceI0..*Reference(Condition | Observation)
instantiatesCanonicalΣ0..*canonical()
instantiatesUriΣ0..*uri
basedOnΣ I0..*Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation)
groupIdentifierΣ0..1Identifier
courseOfTherapyType0..1CodeableConcept
insuranceI0..*Reference(Coverage | ClaimResponse)
note0..*Annotation
sequenceΣ0..1integer
textS Σ0..1string
additionalInstructionΣ0..*CodeableConcept
patientInstructionΣ0..1string
timingΣ0..1Timing
asNeededBooleanboolean
asNeededCodeableConceptCodeableConcept
siteΣ0..1CodeableConcept
routeEDQMΣ0..1CodingBinding
routeSCTCAΣ0..1CodingBinding
RouteOfAdministrationV3PrescribeITΣ0..*CodingBinding
textΣ0..1string
methodΣ0..1CodeableConcept
typeΣ0..1CodeableConcept
doseRangeRange
doseQuantitySimpleQuantity
rateRatioRatio
rateRangeRange
rateQuantitySimpleQuantity
maxDosePerPeriodΣ I0..1Ratio
maxDosePerAdministrationΣ I0..1SimpleQuantity
maxDosePerLifetimeΣ I0..1SimpleQuantity
quantityI0..1SimpleQuantity
durationI0..1Duration
dispenseIntervalI0..1Duration
validityPeriodI0..1Period
numberOfRepeatsAllowed0..1unsignedInt
quantityI0..1SimpleQuantity
expectedSupplyDurationI0..1Duration
performerI0..1Reference(Organization)
allowedBooleanboolean
allowedCodeableConceptCodeableConcept
reason0..1CodeableConcept
priorPrescriptionI0..1Reference(MedicationRequest)
detectedIssueI0..*Reference(DetectedIssue)
eventHistoryI0..*Reference(Provenance)

Key Differences between the IPS-UV and PS-CA

Must Support Differences:

The following elements are considered Must Support in the IPS-UV specification (Continuous Integration build) that are relaxed in this version of the PS-CA profile:

  • MedicationRequest

  • MedicationRequest.requester

  • MedicationRequest.dosageInstruction.timing

  • MedicationRequest.dispenseRequest.validtityPeriod and sub-elements

    Note: Systems that support these elements are encouraged to send them in patient summaries

Cardinality Differences:

  • MedicationRequest.dispenseRequest.validityPeriod minimum cardinality and associated invariant on extension removed.

Vocabulary Differences:

Other differences between the IPS and PS-CA Include:

  • MedicationRequest: comment added describing resource origin
  • MedicationRequest.subject: reference target changed to Patient (PS-CA)
  • MedicationRequest.medicationCodeableConcept: comment added on possible future use of coded values.
  • MedicationRequest.dosageInstruction.route: IPS datatype profile removed