JanuSync Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON
• TTL

Resource Profile: JanuSyncConsentContract - Mappings

Mappings for the janusync-consent-contract resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

Name	Workflow Pattern	RIM Mapping	FiveWs Pattern Mapping
Contract	Request	FinancialContract
id
meta
implicitRules
language
text		Act.text?
contained		N/A
extension		N/A
modifierExtension		N/A
Slices for identifier	Request.identifier	FinancialContract id
identifier:PHI_CODE	Request.identifier	FinancialContract id
id		n/a
extension		n/a
use		Role.code or implied by context
type		Role.code or implied by context
system		II.root or Role.id.root
value		II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period		Role.effectiveTime or implied by context
assigner		II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
url
version
status	Request.status	Act.status	FiveWs.status
legalState
instantiatesCanonical
instantiatesUri
contentDerivative		ActClass: REG (registration) Description: Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role and includes subjects such as lab exam definitions drug protocol definitions prescriptions persons patients practitioners VERIF (Verification) Description: An act which describes the process whereby a 'verifying party' validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details. TRFR (transfer) Description: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD. _ActDetectedIssueManagementCode [abstract term] Description: Codes dealing with the management of Detected Issue observations. _ActInformationAccessContextCode [abstract term] Description: Concepts conveying the context in which authorization given under jurisdictional law by organizational policy or by a patient consent directive permits the collection access Provides codes associated with ActClass value of LIST (working list). RefusalReasonCode [abstract term] Description: Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system having no permission or a detected issue exists which precludes the requested action.	FiveWs.what[x]
issued	Request.authoredOn	A time expression specifying when an Observation Procedure or other Act occurs or depending on the mood is supposed to occur scheduled to occur etc. The activityTime includes the times of component actions (such as preparation and clean-up). For Procedures and SubstanceAdministrations The activityTime is primarily of administrative rather than clinical use. The clinically relevant time is the effectiveTime. When an observation of a prior symptom is made the activityTime describes the time the observation is made as opposed to effectiveTime which is the time the symptom is reported to have occurred. Thus the activityTime may be entirely different from the effectiveTime of the same Act. However even apart from clinical use cases designers should first consider effectiveTime as the primary relevant time for an Act. ActivityTime indicates when an Act occurs not when it is recorded.
applies	Request.occurrence[x]	The clinically or operationally relevant time of an act exclusive of administrative activity.
expirationType
subject	Request.subject	RoleClass RoleCode
authority		OrganizationEntityType Description: Further classifies entities of EntityClass ORG.
domain		Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction). For example TerritoryEntityType Description: A territorial entity that may be cited as the body over which an agency exercises jurisdiction OrganizationEntityType Description: Further classifies entities of EntityClass ORG.
site
name
title
subtitle
alias
author
scope
topic[x]
type	Request.code	In the ActClass Concept Domain: ActClassPolicy. In the ActCode Concept Domain: ActContractType which generalizes ActFinancialContractType ActCoverageType ActBillingArrangementType. ActConsentType which generalizes ActDataConsentType; ActFinancialParticipationConsentType; ActInformationAccessCode; AdvanceBeneficiaryNoticeType. ActPolicyType ActPrivacyPolicyType ActSensitivityPrivacyPolicyType CNTRCT (contract) Description: An agreement of obligation between two or more parties that is subject to contractual law and enforcement A mandate regulation obligation requirement rule The activity of another party; the behavior of another party; or the manner in which an act is executed. LEAF CONCEPTS: JURISPOL (jurisdictional policy) Description:A mandate regulation obligation requirement rule The activity of another party; the behavior of another party; or the manner in which an act is executed.Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program e.g. immunizations methadone treatment A clinical or research protocols imposed by a payer a malpractice insurer An ethical or clinical obligation requirement rule An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria e.g. A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems. CONS (consent)Description: The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures informed consent for clinical trials advanced beneficiary notice against medical advice decline from service release of information agreement etc. The details of consents vary. Often an institution has a number of different consent forms for various purposes including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus Consent is modeled as a special class of Act. The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer" the healthcare provider informing the patient and "consenter" the patient or legal guardian. Some consent may associate a witness or a notary public (e.g. living wills advanced directives). In consents where a healthcare provider is not required (e.g. living will) the performer may be the patient himself or a notary public.	FiveWs.what[x]
id		n/a
extension		n/a
coding		union(. ./translation)
text		./originalText[mediaType/code="text/plain"]/data
subType		_ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. Generalizes: _ActInsurancePolicyCode; _ActInsuranceTypeCode; ActProgramTypeCode. _ActPolicyType Description:Types of policies that further specify the ActClassPolicy value set. Generalizes: _ActPrivacyPolicy; _ActPrivacyLaw; _InformationSensitivityPolicy; ActTrustPolicyType; SecurityPolicy. _ActInvoiceAdjudicationPaymentGroupCode Description: Codes representing adjustments to a Payment Advice such as retroactive clawback garnishee etc. Retroactive adjustment such as fee rate adjustment due to contract negotiations.	FiveWs.what[x]
contentDefinition
id		n/a
extension		n/a
modifierExtension		N/A
type
subType
publisher
publicationDate
publicationStatus
copyright
term		RIM mechanism for grouping or nesting rules which are likely Acts and Observations.	FiveWs.what[x]
id		n/a
extension		n/a
modifierExtension		N/A
identifier	Request.identifier	Act or Observation identifier.
issued	Request.authoredOn	Act availabilityTime	FiveWs.recorded
applies	Request.occurrence[x]	Act effectiveTime	FiveWs.done[x]
topic[x]
type	Request.code	See Contract.term mapping.	FiveWs.what[x]
subType		See Contract.topic mapping.	FiveWs.what[x]
text
securityLabel
id		n/a
extension		n/a
modifierExtension		N/A
number
classification
category
control
offer		Document
id		n/a
extension		n/a
modifierExtension		N/A
identifier
party
id		n/a
extension		n/a
modifierExtension		N/A
reference
role
topic	Event.context	Includes many ActClass ActCode RoleClass RoleCode EntityClass EntityCode ParticipationType codes from HL7 concept domains and code systems. For example HLD (held entity) Description: Entity that is currently in the possession of a holder (scoper) who holds or uses it Scoped by the manufacturer. OWN (owned entity) Description: An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material. WRTE (warranted product) Description: A role a product plays when a guarantee is given to the purchaser by the seller (scoping entity) stating that the product is reliable and free from known defects and that the seller will repair or replace defective parts within a given time limit and under certain conditions.
type		See Contract.term mapping.	FiveWs.what[x]
decision		_ActConsentDirective [abstract term] Description: Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context and are considered closely related or synonymous from a legal perspective.	FiveWs.what[x]
decisionMode
answer
id		n/a
extension		n/a
modifierExtension		N/A
value[x]
text		Document.text
linkId		.outboundRelationship[typeCode=DEFN].target[classCode=OBS moodCode=DEFN].id
securityLabelNumber
asset		FinancialContract.paymentTermsCode
id		n/a
extension		n/a
modifierExtension		N/A
scope
type
typeReference
subtype
relationship		FinancialContract.code
context
id		n/a
extension		n/a
modifierExtension		N/A
reference
code
text
condition
periodType		FinancialContract.code
period		FinancialContract.activityTime
usePeriod		FinancialContract.effectiveTime
text
linkId
answer
securityLabelNumber
valuedItem		COCT_RM440000UV09 ValuedItem classCode INVE
id		n/a
extension		n/a
modifierExtension		N/A
entity[x]		COCT_RM440000UV09 ValuedItem code	FiveWs.what[x]
identifier		COCT_RM440000UV09 ValuedItem id
effectiveTime		COCT_RM440000UV09 ValuedItem effectiveTime	FiveWs.done[x]
quantity		COCT_RM440000UV09 ValuedItem unitQuantity	FiveWs.what[x]
unitPrice		COCT_RM440000UV09 ValuedItem unitPriceAmt	FiveWs.what[x]
factor		COCT_RM440000UV09 ValuedItem factorNumber	FiveWs.what[x]
points		COCT_RM440000UV09 ValuedItem pointNumber	FiveWs.what[x]
net		COCT_RM440000UV09 ValuedItem netAmt	FiveWs.what[x]
payment
paymentDate
responsible
recipient
linkId
securityLabelNumber
action		Participation
id		n/a
extension		n/a
modifierExtension		N/A
doNotPerform
type	Request.performer	RIM Role Participation Type classes
subject
id		n/a
extension		n/a
modifierExtension		N/A
reference
role		RoleClass RoleCode ParticipationType ParticipationFunction codes
intent	Request.reasonCode	ActCoverageReason Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions including criteria for eligibility coverage limitations coverage maximums The rationale or purpose for an act relating to the management of personal information Specifies the reason that a test was performed or observation collected in a clinical research study. SafetyInvestigationReportReasonType Description: Possible reasons generating a report providing information developed during the investigation of an adverse event or a product problem. ControlActReason Description: Indicates the motivation The reason the action was not performed e.g. why the medication was not taken. If an action was not performed Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system having no permission QUALIMP (quality improvement) Description:Operational activities conducted for the purposes of improving the quality of an activity product A collection of concepts identifying why the patient's profile is being queried. _ActInformationManagementReason Description:The rationale or purpose for an act relating to information management Types of reasons why a substance is invalid for use. _NonPerformanceReasonCode Description: The reason the action wasn't performed e.g. why the medication was not taken. If an action wasn"t performed it is often clinically important to know why the action wasn"t taken.	FiveWs.why[x]
linkId
status
context
contextLinkId
occurrence[x]
requester
requesterLinkId
performerType
performerRole
performer
performerLinkId
reasonCode
reasonReference
reason
reasonLinkId
note
securityLabelNumber
group		RIM Grouping or Nesting mechanisms	FiveWs.what[x]
supportingInfo
relevantHistory
signer		Participation
id		n/a
extension		n/a
modifierExtension		N/A
type		RoleClass RoleCode ParticipationType ParticipationFunction class codes.	FiveWs.actor
party	Request.requester	Role Class	FiveWs.author
signature		: CD (0..1) Definition: Whether the participant has attested participation through a signature A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon : ED (0..1) Definition: A textual or multimedia depiction of the signature by which the participant endorses and accepts responsibility for his or her participation in the Act as specified in the Participation.typeCode. UsageNotes: The signature can be represented either inline or by reference according to the ED data type. Typical cases are 1) Paper-based signatures: the ED data type may refer to a document or other resource that can be retrieved through an electronic interface to a hardcopy archive. 2) Electronic signature: this attribute can represent virtually any electronic signature scheme. 3) Digital signature: this attribute can represent digital signatures by reference to a signature data block that is constructed in accordance to a digital signature standard such as XML-DSIG PKCS#7 PGP 1) An "author" participant assumes accountability for the truth of the Act statement to the best of his knowledge. 2) An information recipient only attests to the fact that he or she has received the information.	FiveWs.author
id		n/a
extension		n/a
type
when
who
onBehalfOf
targetFormat
sigFormat
data
friendly		LanguageCommunication	FiveWs.what[x]
id		n/a
extension		n/a
modifierExtension		N/A
content[x]		A renderable textual or multimedia description (or reference to a description) of the complete information which would reasonably be expected to be displayed to a human reader conveyed by the Act.	FiveWs.what[x]
legal		LanguageCommunication	FiveWs.what[x]
id		n/a
extension		n/a
modifierExtension		N/A
content[x]		Act.text of an Act coded as with ActPrivacyLaw ActPolicy code	FiveWs.what[x]
rule		LanguageCommunication	FiveWs.what[x]
id		n/a
extension		n/a
modifierExtension		N/A
content[x]		templateId 2.16.840.1.113883.3.445.16] This template is used to represent an alternative representation of the Privacy Consent Directive (e.g. ODRL XrML 2.16.840.1.113883.5.1001 HL7ActMood) (CONF:14912) 3. SHALL contain exactly one [1..1] code (CONF:9139)/@code="57016-8" Privacy Policy Acknowledgement Document (CodeSystem: 2.16.840.1.113883.6.1 LOINC) (CONF:9138) It specifies the LOINC code corresponding to "Privacy Policy Acknowledgement Document" type="ANY" (CONF:9140) The value contains the computable representation of the policy. This may be a standard-based access control or attribute control based policy (See "References"). Computable Policy Consent example <!-- Sample computable policy language representation --> <entryRelationship typeCode="COMP"> <templateId root="2.16.840.1.113883.3.445.16" /> <observationMedia classCode="OBS" moodCode="EVN"> <value mediaType="text/xml" representation="TXT"> ... </value> </observationMedia> </entryRelationship>	FiveWs.what[x]
legallyBinding[x]		A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication it would be typical to have a single instance of authentication usually by the assigned individual.
Documentation for this format