DocumentReference

The DocumentReference resource stores the following types of information:

  • Client Data
  • Request PDF
  • Terms of Use

Client Data

Clients such as ODSP will be sending us Referral Number and Member Number data they want to search on. This is where that kind of data will be stored.

Requirements

  • needs to be searchable by key columns
  • multiple clients can be sending in data, needs a type to differentiate the data
  • need to link back to the communication that sent us the data
  • record what Program Area owns this data
  • for ODSP it will only be active records. When a record becomes inactive it will be logically deleted.

Profile - ClientData

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
masterIdentifierΣ0..0Identifier
identifierΣ0..*Identifier
statusΣ ?!1..1codeBinding
docStatusΣ0..0codeBinding
typeΣ0..1CodeableConceptBinding
categoryΣ0..0CodeableConcept
subjectΣ I0..0Reference(Patient | Practitioner | Group | Device)
dateΣ0..1instant
authorΣ I0..*Reference(ProgramArea)
authenticatorI0..0Reference(Practitioner | PractitionerRole | Organization)
custodianI0..0Reference(Organization)
descriptionΣ0..0string
securityLabelΣ0..0CodeableConceptBinding
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
id0..1string
extensionI0..*Extension
contentTypeΣ0..1codeBinding
languageΣ0..1codeBinding
data0..1base64Binary
urlΣ0..1url
sizeΣ0..1unsignedInt
hashΣ0..1base64Binary
titleΣ0..1string
creationΣ0..1dateTime
formatΣ0..1CodingBinding
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
encounterI0..0Reference(Encounter | EpisodeOfCare)
event0..0CodeableConcept
periodΣ I0..0Period
facilityType0..0CodeableConcept
practiceSetting0..0CodeableConcept
sourcePatientInfoI0..0Reference(Patient)
relatedI1..1Reference(Client Communication)

Example - ODSP Referral Record

Command 'json' could not render: File was not found for Example-ODSP-Referral-Record


Request PDF

The application generates a PDF version of a request, this is how it is stored.

Requirements

  • to do

Profile - Request PDF

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
masterIdentifierΣ0..0Identifier
id0..1string
extensionI0..*Extension
useΣ ?!0..0codeBinding
systemΣ1..1uriBinding
valueΣ1..1string
periodΣ I0..0Period
assignerΣ I0..0Reference(Organization)
statusΣ ?!1..1codeBindingFixed Value
docStatusΣ0..0codeBinding
id0..1string
extensionI0..*Extension
id0..1string
extensionI0..*Extension
systemΣ1..1uriFixed Value
versionΣ0..0string
codeΣ0..1codeBindingFixed Value
displayΣ0..0string
userSelectedΣ0..0boolean
textΣ0..0string
categoryΣ0..0CodeableConcept
subjectΣ I0..0Reference(Patient | Practitioner | Group | Device)
dateΣ0..0instant
authorΣ I1..1Reference(FlexFormsRole)
authenticatorI0..0Reference(Practitioner | PractitionerRole | Organization)
custodianI0..0Reference(Organization)
descriptionΣ0..0string
securityLabelΣ0..0CodeableConceptBinding
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
id0..1string
extensionI0..*Extension
contentTypeΣ0..1codeBinding
languageΣ0..0codeBinding
data0..0base64Binary
urlΣ0..1url
sizeΣ0..1unsignedInt
hashΣ0..1base64Binary
titleΣ0..1string
creationΣ0..0dateTime
formatΣ0..0CodingBinding

Example - Request PDF that passed validation

Command 'json' could not render: File was not found for Example-Request-PDF


Terms of Use

The Terms of Use is a contract the Program creates, users are challenged to accept the Terms of Use in the application before they can continue. There are 4 types of Terms of Use.

Requirements

  • to do

Profile - Request PDF

Command 'tree' could not render: File was not found for specialauthorizationdigitalinformationexchange2/termsofuse

Example - Request PDF that passed validation

Command 'json' could not render: File was not found for Example-TermsofUse