IHE PCC Referral Status Query
0.0.1-current - ci-build International flag

IHE PCC Referral Status Query, published by IHE Patient Care Coordination Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/PCC.SDOH.RSQ/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

SDOH Referral Status Query Client

CapabilityStatement for Client Actor in the IHE IT Infrastructure Technical Framework Supplement IHE FHIR Scheduling. See https://profiles.ihe.net/ITI/TF/Volume1/ch-38.html. The IHE Profile text is Normative, this conformance resource is Informative.
ToDo Server Actor

CapabilityStatement for Server Actor.

Explain

  • blah
  • blah

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

IHE ToDo Blood Pressure Observation

A profile on the Observation that declares how ToDo will Create/Update blood pressure measurements.

  • must have vital-signs category
  • must have LOINC#55284-4 code AND LOINC#8716-3
  • must have effectiveDateTime
  • must not have a value[x]
  • must have two components
  • must have systolic and diastolic component values in mm[Hg]
  • may have a heart-rate component
  • may have a position component
  • must have status at final
  • must point at the patient
  • may have a note (comment)
  • once created will or might have an id, versionId, lastUpdated, text, and identifier
IHE ToDo BodyWeight Observation

A profile on the Observation that declares how ToDo will Create/Update for body weight measurements.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

The methods of measurement for blood pressure

These are the loinc body positions that IHE ToDo supports on blood pressure.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example Encounter

holding typical values
Example Patient

The patient from which all the example relate
Example of an IHE ToDo blood pressure R4 observation, minimal

holding typical values
Example of an ToDo bodyWeight R4 observation

Sample for demonstration purposes of a common weight Observation

  • marked as compliant with IHE.ToDo.bodyWeight profile
  • marked as test data
  • status of final
  • category vital-signs
  • code of loinc body weight
  • subject of the example patient
  • effective time of December 25th, 2004
  • weight 185 pounds
  • note: a bit heavy
Example of an valid FHIR bodyWeight R4 observation, but not compliant with the profile

Sample for demonstration purposes of a common weight Observation.

  • Given that this is not compliant, it is thus not declaring that it is compliant, it is just an Observation
  • marked as test data
  • status of final
  • category of vital-signs
  • code of loinc 29463-7 and 3141-9
  • also code of snomed 27113001
  • subject of the example patient
  • linked to an encounter
  • effectiveDateTime = March 28, 2016
  • weight 20 stone
  • note: a bit heavy, about 280 lbs