Page tree
Skip to end of metadata
Go to start of metadata

Here are the tracker items for the US Core variances to Patient and MedicationRequest. The trackers contain links to the Real-time Pharmacy Benefit Check IG-defined profiles we propose to use instead.


Issue Type

Key

Status

Resolution

Summary

Reporter

Created

Updated

Priority

Assignee



Change Request

FHIR-27733

Submitted

Unresolved

US Core MedicationRequest variance – dosageInstruction

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27732

Submitted

Unresolved

US Core MedicationRequest variance – encounter

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27731

Submitted

Unresolved

US Core Patient variance – Patient.telecom

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27730

Submitted

Unresolved

US Core Patient variance – Patient.communication.language

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27729

Submitted

Unresolved

US Core Patient variance – us-core-birthsex

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27728

Submitted

Unresolved

US Core Patient variance – us-core-ethnicity

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned


Change Request

FHIR-27727

Submitted

Unresolved

US Core Patient variance – us-core-race

Frank McKinney

5/26/2020

5/26/2020

Medium

Unassigned




And below is a summary of the variances:


MedicationRequest

http://build.fhir.org/ig/HL7/carin-rtpbc/StructureDefinition-rtpbc-patient.html

This profile constrains the MedicationRequest resource to convey a subset of prescription information required in the consumer real-time pharmacy benefit check (RTPBC) process. The content specifies the prescribed product and quantity, and references the prescribing practitioner and the patient’s preferred pharmacy.


This profile differs from the US Core MedicationRequest in that it doesn’t set the encounter or dosageInstruction elements as Must Support, because clients in the exchange will typically be mobile consumer applications that do not possess this information, and because that information is not pertinent to this use case.



Patient

http://build.fhir.org/ig/HL7/carin-rtpbc/StructureDefinition-rtpbc-patient.html

This profile constrains the Patient resource for carrying the limited patient information required in the consumer real-time pharmacy benefit check (RTPBC) process.


The profile differs from the US Core Patient profile in certain respects. It does not contain the us-core-race, us-core-ethnicity or us-core-birthsex extensions, and the Patient.communication.language and Patient.telecom elements are not set to Must Support; these variances reflects that clients in the exchange will typically be mobile consumer applications that do not posess this information, and that the information is not pertinent to this use case.


The RTPBC profile further constrains certain US Core and base elements in a manner that is compatible with the the US Core profile (e.g., tightening element cardinality and further limiting allowed terminology).


  • No labels