QuestionnaireResponseSe

Introduction

The QuestionnaireResponseSe profile includes the answers to the questions in the QuestionnaireSe profile. The QuestionnaireSe profile also defines the logic which the QuestionnaireResponse should follow. QuestionnaireResponseSe is profiled for the Swedish market.

Intended Use

Intended user of the API is a healthcare professional with a specified HSA ID. The healthcare professional should have their assignment and be connected to the specified unit. Unit should also be specified with HSA ID. Intended use in is that the API is used within the same caregiver.

The user and specified unit should exist in COSMIC and be the same in the external system. Only signed notes should be sent from the external system.

It is recommended to implement the API for real time synchronization, due to the patient risk with not having the latest information in COSMIC.

In cases where the patient is the author, the extension common-hsaHierarchy is used to specify to which care provider and unit responsible care unit the QuestionnaireResponse belongs.

A QuestionnaireResponse sent through this API can only reference a Questionnaire which exists in COSMIC. This means that it is a prerequisite to also implement QuestionnaireSeLite and QuestionnaireSe to retrieve an applicable Questionnaire id.

Medical record notes created through this API will be read-only and cannot be updated in the external system. The reason is to avoid differences in documentation between different systems. If the external system has its own storage it should be considered the information owner and every change/update of the information should be done from the external system to guarantee the correctness of the information.

Specific Rules and Limitations

Type Description
Rule The API should not be used to transfer data between care givers.
Rule The API should not be used to send unsigned data to COSMIC.
Rule If a created QuestionnaireResponse is re-signed/updated in the external system it should invalidated and re-created through this API and Provenance API, as there is no support for updating in the current version of COS.
Rule The API does not support scenarios concerning reviewing medical record notes, meaning that the healthcare professional (user) can sign themselves without needing review from others.
Rule Caregivers who use this API must themselves develop routines for how imported information is to be paid attention to.
Rule A date is required. Format for date should be YYYY-MM-DD. If the date is the 1st of respective month, time must also be provided.
Rule Medical record notes created through this API will be read-only and cannot be updated in the external system.
Limitation COSMIC only supports statuses 'completed', 'entered-in-error' and 'in-progress'.

Profile Overview

QuestionnaireResponseSe

idΣ0..1string
id0..1string
extensionI0..*Extension
versionIdΣ0..1id
lastUpdatedΣ0..1instant
sourceΣ0..1uri
profileΣ1..1canonical(StructureDefinition)
securityΣ0..*CodingBinding
tagΣ0..*Coding
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
id0..1string
id0..1string
extensionI0..*Extension
url1..1uriFixed Value
id0..1string
extensionI0..*Extension
referenceΣ I0..1string
typeΣ0..1uriBindingFixed Value
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ1..1uriFixed Value
valueΣ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
displayΣ0..1string
valueReferenceReference()
url1..1uriFixed Value
readOnlyI0..1Extension(boolean)
modifierExtension?! I0..*Extension
identifierΣ0..0Identifier
basedOnΣ I0..0Reference(CarePlan | ServiceRequest)
partOfΣ I0..0Reference(Observation | Procedure)
questionnaireΣ1..1canonical(QuestionnaireSe)
statusΣ ?!1..1codeBinding
id0..1string
extensionI0..*Extension
referenceΣ I0..1string
typeΣ0..1uriBindingFixed Value
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ0..1uri
valueΣ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ1..1uriFixed Value
valueΣ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ1..1uriFixed Value
valueΣ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
displayΣ0..1string
encounterΣ I0..1Reference(Encounter)
authoredΣ1..1dateTime
id0..1string
extensionI0..*Extension
referenceΣ I0..1string
typeΣ1..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
sourceΣ I0..0Reference(Patient | Practitioner | PractitionerRole | RelatedPerson)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
linkId1..1string
definition0..1uri
text0..1string
id0..1string
unsupportedAnswerI0..1Extension(boolean)
modifierExtensionΣ ?! I0..*Extension
valueBooleanboolean
valueDecimaldecimal
valueIntegerinteger
valueDatedate
valueDateTimedateTime
valueTimetime
valueStringstring
valueUriuri
valueAttachmentAttachment
valueCodingCoding
valueQuantityQuantity
valueReferenceReference(ProcedureKVALite | ConditionDiagnosisSe)
item0..*see (item)
item0..*see (item)

Statuses

FHIR status Status in COSMIC
Completed Signed (when author is a PractitionerRole), Complete Not Signable (when author is the patient)

Versions

COS version Profile version Required COSMIC version Date Description
TBA 2.0.0 3.10.0 Sep 2024 hsaHierarchy extension updated to support hsaDepartment.
4.5.0 1.2.0 3.10.0 Sep 2024 readOnly extention added.
4.2.0 1.1.0 3.10.0 Apr 2024 Support for status 'in-progress'.
2.4.0 1.0.0 R8.3.04 Feb 2022 Initial version, support for POST.

Supported Operations

HTTP Methods

Method Description
POST Used to create a QuestionnaireResponse for a given patient. If successful, the operation will return id in response.

Query Operations

Supported Queries

  1. POST [baseURL]/QuestionnaireResponse (Post)

Error Codes

In below table, a few error messages specific for QuestionnaireResponse are listed.

Code Description Comment
400 Invalid payloads