StructureDefinition-pacio-fs

Sourcehl7.fhir.us.pacio-fs#current:PACIO Functional Status Implementation Guide (v4.0.1)
resourceTypeStructureDefinition
idpacio-fs
canonicalhttp://hl7.org/fhir/us/pacio-fs/StructureDefinition/pacio-fs
version1.0.0
statusactive
publisherHL7 Patient Care Work Group
nameFunctionalStatus
titlePACIO Functional Status
date2021-11-03T18:56:23+00:00
descriptionAn exchange of functional status observation for a patient. This profile is used for exchanging a single observation data generally included in a set of observation data collected through the use of a structured resource (e.g. assessment tool, instrument, or screen).
jurisdictionsus
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeObservation
derivationconstraint
basehttp://hl7.org/fhir/StructureDefinition/Observation
Usages
Name Flags Card. Type Description & Constraints doco
. . Observation Observation
. . . Slices for extension Slice: Unordered, Open by value:url
. . . event-location S 0..1 Reference (US Core Location Profile) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/us/pacio-fs/StructureDefinition/event-location
. . . basedOn Currently not used in FunctionalStatus.
. . . partOf Currently not used in FunctionalStatus.
. . . status Should have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.
. . . Slices for category 1 .. A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code.
Slice: Unordered, Open by pattern:coding
. . . . category:functioning 1..1 Binding: PACIO Functioning Category Value Set ( extensible )
. . . . . coding 1.. Required Pattern: At least the following
. . . . . . system 1..1 uri Identity of the terminology system
Fixed Value: http://hl7.org/fhir/us/pacio-fs/CodeSystem/pacio-cat-fs
. . . . . . code 1..1 code Symbol in syntax defined by the system
Fixed Value: functioning
. . . . . . display 1..1 string Representation defined by the system
Fixed Value: Functioning
. . . code For a Post-Acute Care Assessment, code should be a LOINC code and text for the question or concept name.
Binding: LOINC Codes ( extensible )
. . . subject 1.. Reference (US Core Patient Profile) Subject should only be Patient for functional status
. . . focus Currently not used in FunctionalStatus.
. . . encounter Reference (US Core Encounter Profile)
. . . effective[x] 1.. dateTime
. . . issued Currently not used in FunctionalStatus.
. . . performer 1.. Reference (US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile) The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.
. . . value[x] Whenever possible should use the CodeableConcept datatype to provide a suitable code to define the concept for the observation data. As for values like an assessment score or roll-up value, the datatype for this element should be determined by Observation.code. However, for values that are ordinal, may use the CodeableConcept datatype along with the Ordinal Value Extension.
. . . interpretation Currently not used in FunctionalStatus.
. . . bodySite Currently not used in FunctionalStatus.
. . . method Currently not used in FunctionalStatus.
. . . specimen Currently not used in FunctionalStatus.
. . . device Currently not used in FunctionalStatus.
. . . referenceRange Currently not used in FunctionalStatus.
. . . hasMember Currently not used in FunctionalStatus.
. . . derivedFrom S Reference (SDC Questionnaire Response) Should point back to the SDC QuestionnaireResponse that this resource is derived from.
. . . component Currently not used in FunctionalStatus.

doco Documentation for this format

Produced 06 Apr 2023