Used to link an observation (intent or actual) to a goal to indicate that the observation evaluates the goal (for instance, a source observation of "walking distance" evaluates a target goal of "adequate walking distance"). |
|
MFST (is manifestation of) |
[Observation] |
Used to say that the source is a manifestation of the target (for instance, source "hives" is a manifestation of target "penicillin allergy"). |
|
REFR (refers to) |
[Act | Observation | Procedure | SubstanceAdministration
| Supply] |
Used to show a general relationship between the source and the target, when the more specific semantics of the relationship isn't known. |
|
RSON (has reason) |
[Act | Encounter | Observation | Procedure
| SubstanceAdministration | Supply] |
Used to show the reason or rational for a service (for instance source "treadmill test" has reason "chest pain"). |
|
SAS (starts after start) |
[Act | Encounter | Observation | Procedure
| SubstanceAdministration | Supply] |
The source Act starts after the start of the target Act (for instance source "diaphoresis" starts after the start of target "chest pain"). |
|
SPRT (has support) |
[Observation] |
Used to show that the target provides supporting evidence for the source (for instance source "possible lung tumor" has support target "mass seen on chest-x-ray"). |
|
SUBJ (has subject) |
[Observation | RegionOfInterest] |
Used to relate a source region of interest to a target image, or to relate an observation to its subject observation (for instance, source "moderate severity" has subject target "chest pain"). The ActRelationshipType "has subject" is similar to the ParticipationType "subject". Entries that primarily operate on physical subjects use the Participation, whereas entries that primarily operate on other entries use the ActRelationship. |
|
XCRPT (is excerpt of) |
[Act | Observation] |
Used to show that the source is excerpted from the target (for instance source "hemoglobin value of 12" is an excerpt of target "complete blood count"). The distinction between an excerpt and an informant participant can be blurry — such as in the case of recording a patient's medication history where the clinician may obtain the information from an informant or may excerpt the information from another computer system. An informant (or source of information) is a person who provides relevant information. An informant class is in the header, and can be overridden in the body. An excerpt is a sub portion of some other act. |
The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed. In the example in the table above, "treadmill test" RSON (has reason) "chest pain". Inverted, this would have "chest pain" as the source and "treadmill test" as the target: "chest pain" RSON (inverted) "treadmill test". Inversion can be useful when the current context is describing the target of an act relationship that needs to be related back to the source.
The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute (see CDA Context (§ 4.4 )) in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.
CDA entries can reference external objects such as external images and prior reports. These external objects are not part of the authenticated document content. They contain sufficient attributes to enable an explicit reference rather than duplicating the entire referenced object. The CDA entry that wraps the external reference can be used to encode the specific portions of the external reference that are addressed in the narrative block.
Each object allows for an identifier and a code, and contains the RIM Act.text attribute, which can be used to store the URL and MIME type of the object. External objects always have a fixed moodCode of "EVN".
The reference class contains the attribute reference.seperatableInd, which indicates whether or not the source is intended to be interpreted independently of the target. The indicator cannot prevent an individual or application from separating the source and target, but indicates the author's desire and willingness to attest to the content of the source if separated from the target. Typically, where seperatableInd is "false", the exchanged package should include the target of the reference so that the recipient can render it.
A description of allowable reference.typeCode values are shown in the following table. As in the table above (CDA entryRelationship Types), the following table is a guideline for reasonable relationships between CDA entries and external objects, and is not a conformance constraint.
| ActRelationship Type | Reasonable Source and Target classes | Comments |
|---|---|---|
|
ELNK (episode link) |
[Observation] |
Used to show that the source and the target are part of the same episode (for instance, a diagnosis of "pneumonia" can be linked to an external problem list entry of "pneumonia" to show that the current diagnosis is part of the ongoing episode of pneumonia). |
|
REFR (refers to) |
[Act | Observation | Procedure | SubstanceAdministration
| Supply] |
Used to show a general relationship between the source and the target, when the more specific semantics of the relationship isn't known. |
|
RPLC (replace) |
[Act | Encounter | Observation | ObservationMedia | Organizer | Procedure | SubstanceAdministration
| Supply] |
Used to indicate that the source entry is a replacement for the target external act. |
|
SPRT (has support) |
[Observation] |
Used to show that the target provides supporting evidence for the source. |
|
SUBJ (has subject) |
[Observation | RegionOfInterest] |
Used to relate a source region of interest to a target image, or to relate an observation to its subject observation. |
|
XCRPT (is excerpt of) |
[Act | Observation] |
Used to show that the source is excerpted from the target (for instance "the hemoglobin is 10.7" is an excerpt of an externally referenced "complete blood count"). |
Target classes of the reference relationship include ExternalAct, ExternalDocument, ExternalObservation, and External Procedure.
ExternalAct is a derivative of the RIM Act class, to be used when the other more specific classes are not appropriate.
| Code | Definition |
|---|---|
|
ACT (act) [default] |
A healthcare service. |
|
Any ACT subtype. |
See vocabulary domain "ActClassRoot" for allowable values. |
| Code | Definition |
|---|---|
|
EVN (event) [default] |
An actual occurrence of an event. |
ExternalDocument is a derivative of the RIM Document class, used for representing external documents. ExternalDocument.text is modeled as an ED data type - allowing for the expression of the MIME type of the external document.
| Code | Definition |
|---|---|
|
DOC (document) [default] |
The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper. In the electronic world, a document is a kind of composition that bears resemblance to their paper world counter-parts. Documents typically are meant to be human-readable. HL7's notion of document differs from that described in the W3C XML Recommendation, in which a document refers specifically to the contents that fall between the root element's start-tag and end-tag. Not all XML documents are HL7 documents. |
|
Any DOC subtype |
See vocabulary domain "ActClassDocument" for allowable values. |
| Code | Definition |
|---|---|
|
EVN (event) [default] |
An actual occurrence of an event. |
ExternalObservation is a derivative of the RIM Observation class, used for representing external coded and other observations.
| Code | Definition |
|---|---|
|
OBS (observation) [default] |
Observations are actions performed in order to determine an answer or result value. |
|
Any OBS subtype |
See vocabulary domain "ActClassObservation" for allowable values. |
| Code | Definition |
|---|---|
|
EVN (event) [default] |
An actual occurrence of an event. |
ExternalProcedure is a derivative of the RIM Procedure class, used for representing external procedures.
| Code | Definition |
|---|---|
|
PROC (procedure) [default] |
An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. |
| Code | Definition |
|---|---|
|
EVN (event) [default] |
An actual occurrence of an event. |
CDA context is set in the CDA header and applies to the entire document. Context can be overridden at the level of the body, section, and/or CDA entry.
A document, in a sense, is a contextual wrapper for its contents. Assertions in the document header are typically applicable to statements made in the body of the document, unless overridden. For instance, the patient identified in the header is assumed to be the subject of observations described in the body of the document, unless a different subject is explicitly stated, or the author identified in the header is assumed to be the author of the entire document, unless a different author is explicitly identified on a section. The objective of the CDA context rules are to make these practices explicit with relationship to the RIM, such that a computer will understand the context of a portion of a document the same way that a human interprets it.
At the same time, there is no guarantee that machine processing will identify a mistaken application of contextual rules. If a physician records an "outside diagnosis" in narrative but does not nullify the "informant" context, machine processing will not identify the switch in attribution. This is a special case illustrating the limits of automated validation of electronic records and would apply regardless of the context inheritance mechanism. In other words, from some errors of encoding, there is no recovery other than human review.
CDA's approach to context, and the propagation of that context to nested document components, follows these design principles:
The RIM defines the "context" of an act as those participants of the act that can be propagated to nested acts. In the RIM, whether or not contextual participants do propagate to nested acts depends on whether or not the intervening act relationship between parent and child act allows for conduction of context. The explicit representation of context, and whether or not the context on an act can propagate to nested acts, is expressed via the RIM attributes Participation.contextControlCode and ActRelationship.contextConductionInd. CDA constrains the general RIM context mechanism such that context always overrides and propagates, as shown in the following table.
| RIM attribute | Cardinality | Conformance | Fixed Value |
|---|---|---|---|
|
Participation.contextControlCode |
1..1 |
Mandatory (NULL values not permitted) |
"OP" (overriding, propagating) |
|
ActRelationship.contextConductionInd |
1..1 |
Mandatory (NULL values not permitted) |
"true"* |
* The one exception to this is entryRelationship.contextConductionInd, which is defaulted to "true", but can be changed to "false". See entryRelationship (§ <IP_ADDRESS> ) for details.
Where the context of a nested component is unknown, the propagated context must be overridden with a null-valued component, as shown in the following table.
| Context | Null value representation |
|---|---|
|
Author |
AssignedAuthor.id = NULL; No playing entity; No scoping entity. |
|
Confidentiality |
confidentialityCode = NULL. |
|
Human language |
languageCode = NULL. |
|
Informant |
AssignedEntity.id = NULL; No playing entity; No scoping entity. |
|
Participant |
ParticipantRole.id = NULL; No playing entity; No scoping entity. |
The following exhibit illustrates the CDA context model. ClinicalDocument has an author participant, a confidentialityCode, and a languageCode, all of which will propagate to nested acts. The component act relationship going from ClinicalDocument to bodyChoice has contextConductionInd fixed as "true", thus allowing for the propagation of context. The bodyChoice classes, NonXMLBody and StructuredBody, contain a confidentialityCode and languageCode which can be used to override the value specified in the header. The component act relationship going from StructuredBody to Section has contextConductionInd fixed at "true", thus the context on StructuredBody will propagate through to Section. Section can override confidentialityCode, languageCode, and author. A null value for the Section's author participant indicates that the author for that particular section is unknown.
Link to wide graphic (opens in a new window) |
Because context is always overriding and propagating, one can compute the context of a given node by looking for the most proximate assertion. The following example is a sample XPath expression that can be used to identify the <author> context of a section or entry:
(ancestor-or-self::*/author)[position()=last()] |
NOTE: The definitive description of HL7 Hierarchical Description development and interpretation can be found here.
The CDA Hierarchical Description POCD_HD000040 as an Excel View can be found here.
The CDA HD is the definitive source for CDA conformance rules, and serves as the source from which the CDA Schema is derived. While a CDA instance must validate against the CDA Schema, it must also adhere to the conformance rules stated in the CDA Hierarchical Description, and to the rules expressed in the narrative of this specification.
HL7 enables conformance specification at the level of each RIM attribute. RIM attributes can be defined as "Required", in which case the originator must populate the attribute where a value is known even if the cardinality is optional, and "Mandatory", in which case the originator must populate the attribute with a non-NULL value in all cases.
In CDA, Release Two, the "Required" and "Mandatory" conformance indicators are applied as follows:
Note: Note that where Mandatory attributes have a default or fixed value supplied in the CDA HD, the instance need not contain a value. In such cases, the receiver must assume the default value.
Note: The definitive description of HL7 XML Implementation Technology Specification and the process used to go from Hierarchical Description to Schema can be found here.
Implementation Note: The Clinical Document Architecture specification CDA-R2 was originally published as part of HL7's Normative Edition 2005, and this content has been widely distributed to implementers. The schemas referenced below are drawn from Normative Edition 2005. Implementers should use these local schemas, and NOT the schemas of the same name that are in the "processable" directory of the Normative Edition, because the latter schemas include codes that are not compatible with implementations of the earlier specification.
The CDA Schema can be found here
The Datatypes.xsd file can be found here
The Datatypes-base.xsd file can be found here
The POCD_MT000040.xsd file can be found here
The CDA Narrative Block schema can be found here.
The voc.xsd file can be found here.
The CDA Schema is not itself a normative artifact. Rather, checking an instance against the CDA Schema is a surrogate for validating conformance against the normative XML ITS.
The CDA Narrative Block, which is the XML content model of section.text, is manually crafted, as described above (see Section Narrative Block (§ 4.3.5 )). Note that while the CDA Schema is not a normative artifact, the CDA Narrative Block schema is.
Good Health Clinic Consultation note
Consultant: Robert Dolin, MD
Date: April 7, 2000
Patient: Henry Levin, the 7th; MRN: 12345; Sex: Male
Birthdate: September 24, 1932
History of Present Illness
Henry Levin, the 7th is a 67 year old male referred for further asthma management. Onset of asthma in his teens. He was hospitalized twice last year, and already twice this year. He has not been able to be weaned off steroids for the past several months.
Past Medical History
Medications
Allergies and Adverse Reactions
Family History
Social History
Physical Exam
| Date / Time | April 7, 2000 14:30 | April 7, 2000 15:30 |
|---|---|---|
| Height | 177 cm (69.7 in) | |
| Weight | 194.0 lbs (88.0 kg) | |
| BMI | 28.1 kg/m2 | |
| BSA | 2.05 m2 | |
| Temperature | 36.9 C (98.5 F) | |
| Pulse | 86 / minute | 84 / minute |
| Rhythm | Regular | Regular |
| Respirations | 16 / minute, unlabored | 14 / minute |
| Systolic | 132 mmHg | 135 mmHg |
| Diastolic | 86 mmHg | 88 mmHg |
| Position - Cuff | Left Arm | Left Arm |
Labs
In-office Procedure
Assessment
Plan
Signed by: Robert Dolin, MD April 8, 2000
This is a valid and conformant CDA instance based on the sample document above.
NOTE: Readers should be aware of the evolving "Using SNOMED CT in HL7 Version 3" implementation guide, currently in a draft state. The guide, co-developed by HL7 and the College of American Pathologists, will be balloted by HL7 as an Informative Document. Recommendations in the final published guide should usurp patterns of SNOMED CT usage found in this sample instance
This is a sample CDA XSLT style sheet that can be used to transform a CDA instance into HTML. It is provided as a convenient starting point for local style sheet development, and has several known limitations, including:
Introduction
There are an ever-increasing variety of tools and techniques for creating CDA documents:
This appendix considers not the specific tools and technologies, but is intended as a general guide to use of CDA in document creation.
Before you start: RIM compliance
Creating a CDA-compliant instance, by definition, means that the information contained within is defined by the HL7 RIM. Regardless of your starting point or method of document generation, when you are done, the computable semantics of the document will derive their meaning from the relationship between RIM classes, controlled vocabulary and the V3 RIM datatypes. Any CDA-generation implementation must start with an examination of how document requirements relate to the RIM, the datatypes and vocabulary.
The RIM, however, is a highly abstract model and recognizes many extensive vocabulary domains. While RIM-mapping is a necessary condition for CDA generation, it is not sufficient to determine the method of generation or to drive a user interface for document creation.
An exchange specification, not an authoring specification
CDA is a specification for the exchange form of a clinical document. A CDA schema can validate many of the conformance requirements, but will be too general for most authoring applications. In general, standards for interoperability and broadbased exchange will not directly drive an authoring GUI. Given the extent of the CDA domain – clinical care – the requirements for generalized exchange overlap with, but don’t match, the requirements for driving an authoring interface.
For example, the CDA requirement for human readability demands that a single stylesheet render the authenticated clinical content of any CDA document. If CDA elements were defined in the generic schema that corresponds to the sections of a document, <historyOfPresentIllness> or <Subjective>, for example, a stylesheet would need to recognize each of these tags as section-level tags and render them accordingly. The CDA approach, defining <section> and asserting the type of section through coded vocabulary means that not only is the CDA extensible through the externally-maintained vocabulary domains, but that document designers have the flexibility to create hierarchies of sections and to name and tag them according to local requirements, while maintaining compatibility for the exchange context. Thus, while specific tagging that makes it easier to drive a GUI is fine locally, where practice can be more tightly constrained, CDA needs to take a more general approach.
Both sets of requirements, for authoring and for exchange, should be recognized. Within a defined community of interest, such as a single business enterprise, a professional society or in some cases, local and regional health authorities, there can be tight agreement on the form of a document so that the authoring definitions and the exchange definitions coincide. Unless and until there is universal agreement, there can be no universal exchange unless the diversity of local requirements is acknowledged. This is a long-winded way of saying that CDA will remain a general exchange standard, and other approaches must be available to define data entry and document creation validation requirements.
General approaches: constrain or transform
Given that CDA is not an authoring schema, there are two logical alternatives to creating valid CDA instances.
The first is to add constraints to the CDA schema so that the resulting specification defines a particular document type (see the following exhibit "Creating a CDA through a local schema"). There are several technologies available for adding constraints. One approach is to modify the CDA schema itself to a local variant (local.cda.xsd below). Modifications could include limiting the levels of nesting; constraining vocabulary and sequence, for example requiring that a section with a LOINC code for "Subjective" initiate the document body and be followed by a section coded "Objective". These modifications could be expressed in W3C Schema or as Xpath statements within the local schema. Instances that validate against this constrained, local version of CDA are, by definition, also valid CDA instances.
Link to wide graphic (opens in a new window) |
Templates are one type of constraint. HL7 is in the process of defining a formal template mechanism (see The "A" in "CDA" (§ 1.2.2 )).
The second approach is to create a local schema and then transform the local XML instance to CDA
Link to wide graphic (opens in a new window) |
The following table is drawn from LOINC, version 2.14, December 2004, and equals the subset whose scale = "DOC" (and whose status <> "DEL"). The LOINC document model includes a component for "type of service" (conveyed in the Component field), "setting" (conveyed in the System field), "subject matter domain" (conveyed in the Method_Type field), and "training / professional level" (also conveyed in the Method_Type field).
The type of service characterizes the kind of service or activity that was provided to/for the patient (or other subject of the service) as described in the note. Common subclasses of service would be examinations, evaluations, and management. The notion of time sequence, e.g. at the beginning (admission) at the end (discharge) and is subsumed in the axis.
The setting is a modest extension of the Centers for Medicare and Medicaid Services (CMS) coarse definition of settings. Setting is not equivalent to location, which typically has more locally defined meanings.
The subject matter domain characterized the subject matter or clinical categorization of a note. The training / professional level characterizes the training or professional level of the author of the document.
| LOINC_NUM | COMPONENT (Type of Service) | SYSTEM (Setting) | METHOD_TYPE (Subject Matter Domain and/or Training / Professional Level) |
|---|---|---|---|
|
34862-3 |
ADMISSION EVALUATION NOTE |
INPATIENT |
ATTENDING PHYSICIAN.GENERAL MEDICINE |
|
34744-3 |
ADMISSION EVALUATION NOTE |
{SETTING} |
NURSING |
|
34873-0 |
ADMISSION EVALUATION NOTE |
{SETTING} |
SURGERY |
|
34094-3 |
ADMISSION HISTORY AND PHYSICAL NOTE |
HOSPITAL |
CARDIOLOGY |
|
34763-3 |
ADMISSION HISTORY AND PHYSICAL NOTE |
{SETTING} |
GENERAL MEDICINE |
|
28615-3 |
AUDIOLOGY STUDY |
{SETTING} |
|
|
18743-5 |
AUTOPSY NOTE |
{SETTING} |
{PROVIDER} |
|
33720-4 |
BLOOD BANK CONSULT |
{SETTING} |
|
|
34095-0 |
COMPREHENSIVE HISTORY & PHYSICAL NOTE |
{SETTING} |
{PROVIDER} |
|
34096-8 |
COMPREHENSIVE HISTORY AND PHYSICAL |
NURSING HOME |
|
|
34098-4 |
CONFERENCE EVALUATION NOTE |
{SETTING} |
{PROVIDER} |
|
34097-6 |
CONFERENCE EVALUATION NOTE |
NURSING HOME |
{PROVIDER} |
|
24611-6 |
CONFIRMATORY CONSULTATION NOTE |
OUTPATIENT |
{PROVIDER} |
|
34807-8 |
CONSULTATION NOTE |
{SETTING} |
OPHTHALMOLOGY |
|
34100-8 |
CONSULTATION NOTE |
CRITICAL CARE UNIT |
{PROVIDER} |
|
34810-2 |
CONSULTATION NOTE |
{SETTING} |
OPTOMETRY |
|
34812-8 |
CONSULTATION NOTE |
{SETTING} |
OROMAXILLOFACIAL SURGERY |
|
34814-4 |
CONSULTATION NOTE |
{SETTING} |
ORTHOPEDICS |
|
34831-8 |
CONSULTATION NOTE |
{SETTING} |
RADIATION ONCOLOGY |
|
34761-7 |
CONSULTATION NOTE |
{SETTING} |
GASTROENTEROLOGY |
|
34099-2 |
CONSULTATION NOTE |
{SETTING} |
CARDIOLOGY |
|
34833-4 |
CONSULTATION NOTE |
{SETTING} |
RECREATIONAL THERAPY |
|
34820-1 |
CONSULTATION NOTE |
{SETTING} |
PHARMACY |
|
34822-7 |
CONSULTATION NOTE |
{SETTING} |
PHYSICAL MEDICINE AND REHABILITATION |
|
34835-9 |
CONSULTATION NOTE |
{SETTING} |
REHABILITATION |
|
34824-3 |
CONSULTATION NOTE |
{SETTING} |
PHYSICAL THERAPY |
|
34826-8 |
CONSULTATION NOTE |
{SETTING} |
PLASTIC SURGERY |
|
34764-1 |
CONSULTATION NOTE |
{SETTING} |
GENERAL MEDICINE |
|
34837-5 |
CONSULTATION NOTE |
{SETTING} |
RESPIRATORY THERAPY |
|
34803-7 |
CONSULTATION NOTE |
{SETTING} |
OCCUPATIONAL HEALTH |
|
34816-9 |
CONSULTATION NOTE |
{SETTING} |
OTORHINOLARYNGOLOGY |
|
34783-1 |
CONSULTATION NOTE |
{SETTING} |
KINESIOTHERAPY |
|
34756-7 |
CONSULTATION NOTE |
{SETTING} |
DENTISTRY |
|
34788-0 |
CONSULTATION NOTE |
{SETTING} |
PSYCHIATRY |
|
34102-4 |
CONSULTATION NOTE |
HOSPITAL |
PSYCHIATRY |
|
34791-4 |
CONSULTATION NOTE |
{SETTING} |
PSYCHOLOGY |
|
34103-2 |
CONSULTATION NOTE |
{SETTING} |
PULMONARY |
|
34795-5 |
CONSULTATION NOTE |
{SETTING} |
NEPHROLOGY |
|
34758-3 |
CONSULTATION NOTE |
{SETTING} |
DERMATOLOGY |
|
34760-9 |
CONSULTATION NOTE |
{SETTING} |
DIABETOLOGY |
|
34798-9 |
CONSULTATION NOTE |
{SETTING} |
NEUROSURGERY |
|
34800-3 |
CONSULTATION NOTE |
{SETTING} |
NUTRITION+DIETETICS |
|
34749-2 |
CONSULTATION NOTE |
OUTPATIENT |
ANESTHESIA |
|
34781-5 |
CONSULTATION NOTE |
{SETTING} |
INFECTIOUS DISEASE |
|
34828-4 |
CONSULTATION NOTE |
{SETTING} |
PODIATRY |
|
34101-6 |
CONSULTATION NOTE |
OUTPATIENT |
GENERAL MEDICINE |
|
34104-0 |
CONSULTATION NOTE |
HOSPITAL |
{PROVIDER} |
|
34785-6 |
CONSULTATION NOTE |
{SETTING} |
MENTAL HEALTH |
|
34805-2 |
CONSULTATION NOTE |
{SETTING} |
ONCOLOGY |
|
34797-1 |
CONSULTATION NOTE |
{SETTING} |
NEUROLOGY |
|
34879-7 |
CONSULTATION NOTE |
{SETTING} |
ENDOCRINOLOGY |
|
34839-1 |
CONSULTATION NOTE |
{SETTING} |
RHEUMATOLOGY |
|
34779-9 |
CONSULTATION NOTE |
{SETTING} |
HEMATOLOGY+ONCOLOGY |
|
34777-3 |
CONSULTATION NOTE |
{SETTING} |
GYNECOLOGY |
|
34776-5 |
CONSULTATION NOTE |
{SETTING} |
GERONTOLOGY |
|
34855-7 |
CONSULTATION NOTE |
{SETTING} |
OCCUPATIONAL THERAPY |
|
34853-2 |
CONSULTATION NOTE |
{SETTING} |
VASCULAR SURGERY |
|
34771-6 |
CONSULTATION NOTE |
{SETTING} |
GENERAL SURGERY |
|
34841-7 |
CONSULTATION NOTE |
{SETTING} |
SOCIAL WORK |
|
34845-8 |
CONSULTATION NOTE |
{SETTING} |
SPEECH THERAPY+AUDIOLOGY |
|
11488-4 |
CONSULTATION NOTE |
{SETTING} |
{PROVIDER} |
|
34847-4 |
CONSULTATION NOTE |
{SETTING} |
SURGERY |
|
34851-6 |
CONSULTATION NOTE |
{SETTING} |
UROLOGY |
|
34849-0 |
CONSULTATION NOTE |
{SETTING} |
THORACIC SURGERY |
|
34865-6 |
COUNSELING NOTE |
{SETTING} |
PSYCHIATRY |
|
34866-4 |
COUNSELING NOTE |
{SETTING} |
PSYCHOLOGY |
|
34872-2 |
COUNSELING NOTE |
{SETTING} |
SOCIAL WORK |
|
34869-8 |
COUNSELING NOTE |
{SETTING} |
PHARMACY |
|
34864-9 |
COUNSELING NOTE |
{SETTING} |
MENTAL HEALTH |
|
28622-9 |
DISCHARGE ASSESSMENT NOTE |
{SETTING} |
NURSING |
|
28574-2 |
DISCHARGE NOTE |
{SETTING} |
{PROVIDER} |
|
11490-0 |
DISCHARGE SUMMARIZATION NOTE |
{SETTING} |
PHYSICIAN |
|
28655-9 |
DISCHARGE SUMMARIZATION NOTE |
{SETTING} |
ATTENDING PHYSICIAN |
|
18842-5 |
DISCHARGE SUMMARIZATION NOTE |
{SETTING} |
{PROVIDER} |
|
34105-7 |
DISCHARGE SUMMARIZATION NOTE |
HOSPITAL |
{PROVIDER} |
|
29761-4 |
DISCHARGE SUMMARIZATION NOTE |
{SETTING} |
DENTISTRY |
|
34745-0 |
DISCHARGE SUMMARIZATION NOTE |
{SETTING} |
NURSING |
|
34106-5 |
DISCHARGE SUMMARIZATION NOTE |
HOSPITAL |
PHYSICIAN |
|
34902-7 |
EDUCATION NOTE |
OUTPATIENT |
GERONTOLOGY |
|
34897-9 |
EDUCATION NOTE |
{SETTING} |
DIABETOLOGY |
|
34895-3 |
EDUCATION NOTE |
{SETTING} |
{PROVIDER} |
|
34107-3 |
EDUCATION PROCEDURE NOTE |
HOME HEALTH |
{PROVIDER} |
|
34108-1 |
EVALUATION AND MANAGEMENT |
OUTPATIENT |
{PROVIDER} |
|
34836-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
REHABILITATION |
|
34111-5 |
EVALUATION AND MANAGEMENT NOTE |
EMERGENCY DEPARTMENT |
{PROVIDER} |
|
34834-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
RECREATIONAL THERAPY |
|
34759-1 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
DERMATOLOGY |
|
34842-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SOCIAL WORK |
|
34113-1 |
EVALUATION AND MANAGEMENT NOTE |
NURSING HOME |
{PROVIDER} |
|
34762-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GASTROENTEROLOGY |
|
34840-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
RHEUMATOLOGY |
|
34757-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
DENTISTRY |
|
34112-3 |
EVALUATION AND MANAGEMENT NOTE |
INPATIENT |
{PROVIDER} |
|
34746-8 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NURSING |
|
34754-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
CRITICAL CARE |
|
34772-4 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GENERAL SURGERY |
|
34753-4 |
EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
CARDIOLOGY |
|
34752-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
CARDIOLOGY |
|
34832-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
RADIATION ONCOLOGY |
|
34750-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ANESTHESIA |
|
34773-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ATTENDING PHYSICIAN.GENERAL SURGERY |
|
34830-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PULMONARY |
|
34778-1 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GYNECOLOGY |
|
34838-3 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
RESPIRATORY THERAPY |
|
34780-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
HEMATOLOGY+ONCOLOGY |
|
34109-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
{PROVIDER} |
|
34854-0 |
EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
VASCULAR SURGERY |
|
34765-8 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GENERAL MEDICINE |
|
34819-3 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PATHOLOGY |
|
34801-1 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NUTRITION+DIETETICS |
|
34823-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PHYSICAL MEDICINE AND REHABILITATION |
|
34825-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PHYSICAL THERAPY |
|
34827-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PLASTIC SURGERY |
|
34829-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PODIATRY |
|
34846-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SPEECH THERAPY+AUDIOLOGY |
|
34848-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SURGERY |
|
34815-1 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ORTHOPEDICS |
|
34852-4 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
UROLOGY |
|
34817-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OTORHINOLARYNGOLOGY |
|
34856-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ANTICOAGULATION |
|
34857-3 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SUBSTANCE ABUSE |
|
34858-1 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PAIN MANAGEMENT |
|
34859-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
HYPERLIPIDEMIA |
|
34860-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
HYPERTENSION |
|
34861-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
DIABETOLOGY |
|
34878-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
EMERGENCY MEDICINE |
|
34898-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ENDOCRINOLOGY |
|
34905-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NEUROLOGY |
|
34850-8 |
EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
THORACIC SURGERY |
|
34792-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PSYCHOLOGY |
|
34766-6 |
EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
GENERAL MEDICINE |
|
34767-4 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
MEDICAL STUDENT.GENERAL MEDICINE |
|
34768-2 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NURSE.GENERAL MEDICINE |
|
34769-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ATTENDING PHYSICIAN.GENERAL MEDICINE |
|
34782-3 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
INFECTIOUS DISEASE |
|
34784-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
KINESIOTHERAPY |
|
34786-4 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
MENTAL HEALTH |
|
34821-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PHARMACY |
|
34789-8 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
PSYCHIATRY |
|
34813-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OROMAXILLOFACIAL SURGERY |
|
34802-9 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OCCUPATIONAL HEALTH |
|
34811-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OPTOMETRY |
|
34808-6 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OPHTHALMOLOGY |
|
34806-0 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ONCOLOGY |
|
34804-5 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OCCUPATIONAL THERAPY |
|
34794-8 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
MULTIDISCIPLINARY |
|
34110-7 |
EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
DIABETOLOGY |
|
34799-7 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NEUROSURGERY |
|
34796-3 |
EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NEPHROLOGY |
|
34787-2 |
GROUP COUNSELING NOTE |
{SETTING} |
MENTAL HEALTH |
|
34790-6 |
GROUP COUNSELING NOTE |
{SETTING} |
PSYCHIATRY |
|
34843-3 |
GROUP COUNSELING NOTE |
{SETTING} |
SOCIAL WORK |
|
34114-9 |
GROUP COUNSELING NOTE |
HOSPITAL |
{PROVIDER} |
|
34793-0 |
GROUP COUNSELING NOTE |
{SETTING} |
PSYCHOLOGY |
|
34774-0 |
HISTORY & PHYSICAL NOTE |
{SETTING} |
GENERAL SURGERY |
|
28626-0 |
HISTORY & PHYSICAL NOTE |
{SETTING} |
PHYSICIAN |
|
11492-6 |
HISTORY & PHYSICAL NOTE |
HOSPITAL |
{PROVIDER} |
|
34116-4 |
HISTORY & PHYSICAL NOTE |
NURSING HOME |
PHYSICIAN |
|
34115-6 |
HISTORY & PHYSICAL NOTE |
HOSPITAL |
MEDICAL STUDENT |
|
34117-2 |
HISTORY AND PHYSICAL NOTE |
{SETTING} |
{PROVIDER} |
|
18841-7 |
HOSPITAL CONSULTATIONS |
{SETTING} |
|
|
28572-6 |
INITIAL EVALUATION NOTE |
{SETTING} |
DENTISTRY |
|
28654-2 |
INITIAL EVALUATION NOTE |
{SETTING} |
ATTENDING PHYSICIAN |
|
18735-1 |
INITIAL EVALUATION NOTE |
{SETTING} |
PHYSICAL THERAPY |
|
18736-9 |
INITIAL EVALUATION NOTE |
{SETTING} |
PHYSICIAN |
|
18737-7 |
INITIAL EVALUATION NOTE |
{SETTING} |
PODIATRY |
|
18738-5 |
INITIAL EVALUATION NOTE |
{SETTING} |
PSYCHOLOGY |
|
18739-3 |
INITIAL EVALUATION NOTE |
{SETTING} |
SOCIAL SERVICE |
|
18734-4 |
INITIAL EVALUATION NOTE |
{SETTING} |
OCCUPATIONAL THERAPY |
|
28581-7 |
INITIAL EVALUATION NOTE |
{SETTING} |
CHIROPRACTOR |
|
29753-1 |
INITIAL EVALUATION NOTE |
{SETTING} |
NURSING |
|
28636-9 |
INITIAL EVALUATION NOTE |
{SETTING} |
{PROVIDER} |
|
28635-1 |
INITIAL EVALUATION NOTE |
{SETTING} |
PSYCHIATRY |
|
28621-1 |
INITIAL EVALUATION NOTE |
{SETTING} |
NURSE PRACTITIONER |
|
18763-3 |
INITIAL EVALUATION NOTE |
{SETTING} |
CONSULTING PHYSICIAN |
|
18740-1 |
INITIAL EVALUATION NOTE |
{SETTING} |
SPEECH THERAPY |
|
34120-6 |
INITIAL EVALUATION NOTE |
OUTPATIENT |
{PROVIDER} |
|
34119-8 |
INITIAL EVALUATION NOTE |
NURSING HOME |
{PROVIDER} |
|
34118-0 |
INITIAL EVALUATION NOTE |
HOME HEALTH |
{PROVIDER} |
|
34121-4 |
INTERVENTIONAL PROCEDURE NOTE |
{SETTING} |
|
|
34896-1 |
INTERVENTIONAL PROCEDURE NOTE |
{SETTING} |
CARDIOLOGY |
|
34899-5 |
INTERVENTIONAL PROCEDURE NOTE |
{SETTING} |
GASTROENTEROLOGY |
|
34903-5 |
NOTE |
{SETTING} |
MENTAL HEALTH |
|
34906-8 |
NOTE |
{SETTING} |
PASTORAL CARE |
|
11536-0 |
NOTES |
{SETTING} |
NURSING |
|
34871-4 |
OPERATIVE NOTE |
{SETTING} |
PODIATRY |
|
34874-8 |
OPERATIVE NOTE |
{SETTING} |
SURGERY |
|
34877-1 |
OPERATIVE NOTE |
{SETTING} |
UROLOGY |
|
34870-6 |
OPERATIVE NOTE |
{SETTING} |
PLASTIC SURGERY |
|
34868-0 |
OPERATIVE NOTE |
{SETTING} |
ORTHOPEDICS |
|
34818-5 |
OPERATIVE NOTE |
{SETTING} |
OTORHINOLARYNGOLOGY |
|
34122-2 |
PATHOLOGY PROCEDURE NOTE |
{SETTING} |
PATHOLOGY |
|
34880-5 |
POST-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NURSE.SURGERY |
|
34875-5 |
POST-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SURGERY |
|
34863-1 |
POST-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GENERAL SURGERY |
|
34867-2 |
POST-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
OUTPATIENT |
OPHTHALMOLOGY |
|
34881-3 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NURSE.SURGERY |
|
34123-0 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
HOSPITAL |
ANESTHESIA |
|
34775-7 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
GENERAL SURGERY |
|
34876-3 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
SURGERY |
|
34751-8 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
ANESTHESIA |
|
34809-4 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
OPHTHALMOLOGY |
|
34747-6 |
PRE-OPERATIVE EVALUATION AND MANAGEMENT NOTE |
{SETTING} |
NURSING |
|
28570-0 |
PROCEDURE NOTE |
{SETTING} |
{PROVIDER} |
|
28625-2 |
PROCEDURE NOTE |
{SETTING} |
PODIATRY |
|
28577-5 |
PROCEDURE NOTE |
{SETTING} |
DENTISTRY |
|
11505-5 |
PROCEDURE NOTE |
{SETTING} |
PHYSICIAN |
|
28575-9 |
PROGRESS NOTE |
{SETTING} |
NURSE PRACTITIONER |
|
28580-9 |
PROGRESS NOTE |
{SETTING} |
CHIROPRACTOR |
|
18744-3 |
STUDY REPORT |
RESPIRATORY SYSTEM |
BRONCHOSCOPY |
|
11510-5 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
PSYCHOLOGY |
|
11508-9 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
PHYSICAL THERAPY |
|
11509-7 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
PODIATRY |
|
11506-3 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
{PROVIDER} |
|
11507-1 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
OCCUPATIONAL THERAPY |
|
11512-1 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
SPEECH THERAPY |
|
15507-7 |
SUBSEQUENT EVALUATION NOTE |
EMERGENCY DEPARTMENT |
{PROVIDER} |
|
18733-6 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
ATTENDING PHYSICIAN |
|
34904-3 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
MENTAL HEALTH |
|
34901-9 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
GENERAL MEDICINE |
|
18764-1 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
NURSE PRACTITIONER |
|
34129-7 |
SUBSEQUENT EVALUATION NOTE |
HOME HEALTH |
{PROVIDER} |
|
34132-1 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
PHARMACY |
|
34131-3 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
{PROVIDER} |
|
28656-7 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
SOCIAL SERVICE |
|
34130-5 |
SUBSEQUENT EVALUATION NOTE |
HOSPITAL |
{PROVIDER} |
|
28617-9 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
DENTISTRY |
|
34128-9 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
DENTISTRY |
|
34127-1 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
DENTAL HYGIENIST |
|
34126-3 |
SUBSEQUENT EVALUATION NOTE |
CRITICAL CARE UNIT |
{PROVIDER} |
|
34900-1 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
GENERAL MEDICINE |
|
34125-5 |
SUBSEQUENT EVALUATION NOTE |
HOME HEALTH CARE |
CASE MANAGER |
|
28569-2 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
CONSULTING PHYSICIAN |
|
18762-5 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
CHIROPRACTOR |
|
34124-8 |
SUBSEQUENT EVALUATION NOTE |
OUTPATIENT |
CARDIOLOGY |
|
28627-8 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
PSYCHIATRY |
|
28623-7 |
SUBSEQUENT EVALUATION NOTE |
{SETTING} |
NURSING |
|
34133-9 |
SUMMARIZATION OF EPISODE NOTE |
{SETTING} |
{PROVIDER} |
|
34134-7 |
SUPERVISORY NOTE |
OUTPATIENT |
ATTENDING PHYSICIAN |
|
34135-4 |
SUPERVISORY NOTE |
OUTPATIENT |
ATTENDING PHYSICIAN.CARDIOLOGY |
|
34136-2 |
SUPERVISORY NOTE |
OUTPATIENT |
ATTENDING PHYSICIAN.GASTROENTEROLOGY |
|
28624-5 |
SURGICAL OPERATION NOTE |
{SETTING} |
PODIATRY |
|
28573-4 |
SURGICAL OPERATION NOTE |
{SETTING} |
PHYSICIAN |
|
11504-8 |
SURGICAL OPERATION NOTE |
{SETTING} |
{PROVIDER} |
|
28583-3 |
SURGICAL OPERATION NOTE |
{SETTING} |
DENTISTRY |
|
34137-0 |
SURGICAL OPERATION NOTE |
OUTPATIENT |
{PROVIDER} |
|
34138-8 |
TARGETED HISTORY AND PHYSICAL NOTE |
{SETTING} |
{PROVIDER} |
|
34139-6 |
TELEPHONE ENCOUNTER NOTE |
{SETTING} |
NURSING |
|
34844-1 |
TELEPHONE ENCOUNTER NOTE |
OUTPATIENT |
SOCIAL WORK |
|
34748-4 |
TELEPHONE ENCOUNTER NOTE |
{SETTING} |
{PROVIDER} |
|
34140-4 |
TRANSFER OF CARE REFERRAL NOTE |
{SETTING} |
{PROVIDER} |
|
34770-8 |
TRANSFER SUMMARIZATION NOTE |
{SETTING} |
GENERAL MEDICINE |
|
18761-7 |
TRANSFER SUMMARIZATION NOTE |
{SETTING} |
{PROVIDER} |
|
28651-8 |
TRANSFER SUMMARIZATION NOTE |
{SETTING} |
NURSING |
|
28616-1 |
TRANSFER SUMMARIZATION NOTE |
{SETTING} |
PHYSICIAN |
|
34755-9 |
TRANSFER SUMMARIZATION NOTE |
{SETTING} |
CRITICAL CARE |
|
28568-4 |
VISIT NOTE |
EMERGENCY DEPARTMENT |
PHYSICIAN |
|
28653-4 |
VISIT NOTE |
{SETTING} |
SOCIAL SERVICE |
|
28618-7 |
VISIT NOTE |
{SETTING} |
DENTISTRY |
|
28579-1 |
VISIT NOTE |
{SETTING} |
PHYSICAL THERAPY |
|
28578-3 |
VISIT NOTE |
{SETTING} |
OCCUPATIONAL THERAPY |
|
28571-8 |
VISIT NOTE |
{SETTING} |
SPEECH THERAPY |
|
28628-6 |
VISIT NOTE |
{SETTING} |
PSYCHIATRY |
A long term objective of CDA and other specifications in the V3 family is to achieve increasingly greater and greater "semantic interoperability", which might be defined as the ability of two applications to share data, with no prior negotiations, such that decision support within each application continues to function reliably when processed against the received data.
CDA seeks to achieve the highest level of constraint that can exist in an international standard. Where international consensus is lacking, and where uses cases in different realms currently preclude consensus, CDA will need to be necessarily inclusive. In such areas, ongoing harmonization and consensus building will further enable semantic interopability, which will be reflected in future iterations of CDA.
While the framework provided by the RIM and by CDA and by the shared HL7 Clinical Statement Model are a critical component of semantic interoperability, they are not currently sufficient, particularly given the lack of global terminology solution, and the fact that each terminology overlaps with the RIM in different ways. Such terminology solutions are outside the scope of CDA, and will need to be addressed in various national and international forums.
CDA, Release One became an ANSI-approved HL7 Standard in November, 2000, representing the first specification derived from the HL7 Reference Information Model (RIM). Since then, the RIM has matured, as has the methodology used to derive RIM-based specifications. In addition, early adopters are posing new use cases for incorporation.
The basic model of CDA, Release Two is essentially unchanged. A CDA document has a header and a body. The body contains nested sections. These sections can be coded using standard vocabularies, and can contain "entries". CDA, Release One entries included such things as character data, hyperlinks, and multimedia.
The main evolutionary steps in CDA, Release Two are that both header and body are fully RIM-derived, and there is a much richer assortment of entries to use within CDA sections. CDA, Release Two enables clinical content to be formally expressed to the extent that is it modeled in the RIM.
CDA, Release Two takes advantage of HL7’s growing expertise in creating model-based XML standards. Given the evolution of the RIM and the HL7 development methodology since November 2000, there are a number of changes between the new and the old CDA.
The following components are retained for backwards compatibility with CDA, Release One, and have been deprecated:
Further use of these components is discouraged.
The following tables enumerate CDA R1 components and show the corresponding components in CDA R2. In some cases, such as where CDA R1 was ambiguous or where a CDA R1 participant was split into multiple CDA R2 participants, a formal mapping might need to take local usage into account. In such cases guidance is provided rather than formal rules.
| CDA R1 vocabulary | Corresponding CDA R2 vocabulary | Comments |
|---|---|---|
|
clinical_document_header / document_type_cd <= DocumentType (2.16.840.1.1138<IP_ADDRESS>70) (CWE) |
ClinicalDocument / code <= DocumentType (2.16.840.1.113883.6.1) (CWE) |
|
|
clinical_document_header / confidentiality_cd <= ServiceConfidentiality (2.16.840.1.113883.5.10228) (CWE) |
ClinicalDocument / confidentialityCode <= x_BasicConfidentialityKind (2.16.840.1.113883.5.25) (CWE) |
|
|
clinical_document_header / document_relationship / document_relationship.type_cd <= ServiceRelationship (2.16.840.1.113883.5.10317) (CNE) |
ClinicalDocument / relatedDocument / @typeCode <= x_ActRelationshipDocument (2.16.840.1.113883.5.1002) (CNE) |
|
|
clinical_document_header / fulfills_order / fulfills_order.type_cd <= ServiceRelationship (2.16.840.1.113883.5.10317) (CNE) |
ClinicalDocument / inFulfillmentOf / @typeCode <= FLFS (2.16.840.1.113883.5.1002) (CNE) |
|
|
clinical_document_header / patient_encounter / practice_setting_cd <= PracticeSetting (2.16.840.1.113883.5.10588) (CWE) |
ClinicalDocument / componentOf / encompassingEncounter / location / healthCareFacility / code <= ServiceDeliveryLocationRoleType (2.16.840.1.113883.5.111) (CWE) |
|
|
clinical_document_header / authenticator / authenticator.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / authenticator / @typeCode <= AUTHEN (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / authenticator / signature_cd <= ServiceActorSignature (2.16.840.1.113883.5.10282) (CNE) |
ClinicalDocument / authenticator / signatureCode <= ParticipationSignature (2.16.840.1.113883.5.89) (CNE) |
|
|
clinical_document_header / authenticator / person / person_name / person_name.type_cd <= PersonNamePurpose (2.16.840.1.113883.5.200) (CWE) |
ClinicalDocument / authenticator / assignedEntity / assignedPerson / name / @use <= PersonNameUse (2.16.840.1.113883.5.45) (CNE) |
|
|
clinical_document_header / legal_authenticator / authenticator.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / legalAuthenticator / @typeCode <= LA (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / legal_authenticator / signature_cd <= ServiceActorSignature (2.16.840.1.113883.5.10282) (CNE) |
ClinicalDocument / legalAuthenticator / signatureCode <= ParticipationSignature (2.16.840.1.113883.5.89) (CNE) |
|
|
clinical_document_header / intended_recipient / intended_recipient.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / intendedRecipient / @typeCode <= x_InformationRecipient (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / originator / originator.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / author / @typeCode <= AUT (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / originating_organization / originating_organization.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / custodian / @typeCode <= CST (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / transcriptionist / transcriptionist.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) |
ClinicalDocument / dataEnterer / @typeCode <= ENT (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / provider / provider.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CNE) (Value set "ASS", "CON", "PRF") |
ClinicalDocument / serviceEvent / performer / @typeCode <= x_ServiceEventPerformer (2.16.840.1.113883.5.90) (CNE) (Value set "PRF", "PPRF", "SPRF") ClinicalDocument / encompassingEncounter / responsibleParty / @typeCode <= RESP (2.16.840.1.113883.5.90) (CNE) ClinicalDocument / encompassingEncounter / encounterParticipant / @typeCode <= x_EncounterParticipant (2.16.840.1.113883.5.90) (CNE) (Value set "ADM", "ATND", "CON" , "DIS" , "REF") |
|
|
clinical_document_header / provider / function_cd <= ServiceActorFunction (2.16.840.1.113883.5.10267) (CWE) |
ClinicalDocument / serviceEvent / performer / functionCode <= ParticipationFunction (2.16.840.1.113883.5.88) (CWE) |
|
|
clinical_document_header / service_actor / service_actor.type_cd <= ServiceActor (2.16.840.1.113883.5.10246) (CWE) |
ClinicalDocument / participant / @typeCode <= ParticipationType (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / service_actor / signature_cd <= ServiceActorSignature (2.16.840.1.113883.5.10282) (CNE) |
ClinicalDocument / authenticator / signatureCode <= ParticipationSignature (2.16.840.1.113883.5.89) (CNE) |
|
|
clinical_document_header / patient / administrative_gender_cd <= AdministrativeGender (2.16.840.1.113883.5.1) (CWE) |
ClinicalDocument / recordTarget / patientRole / patient / administrativeGenderCode <= AdministrativeGender (2.16.840.1.113883.5.1) (CWE) |
|
|
clinical_document_header / originating_device / originating_device.type_cd <= ServiceTargetType (2.16.840.1.113883.5.10285) (CNE) |
ClinicalDocument / author / @typeCode <= AUT (2.16.840.1.113883.5.90) (CNE) |
|
|
clinical_document_header / originating_device / device / responsibility / responsibility.type_cd <= MaterialResponsibility (2.16.840.1.113883.5.10416) (CWE) |
ClinicalDocument / author / assignedAuthor / assignedAuthoringDevice / asMaintainedEntity / @classCode <= MNT (2.16.840.1.113883.5.110) (CNE) |
|
|
clinical_document_header / service_target / service_target.type_cd <= ServiceTargetType (2.16.840.1.113883.5.10285) (CWE) |
ClinicalDocument / participant / @typeCode <= ParticipationType (2.16.840.1.113883.5.90) (CNE) |
|
|
section / caption / caption_cd (CWE) |
section / code <= DocumentSectionType (2.16.840.1.113883.6.1) (CWE) |
|
|
caption / caption_cd (CWE) |
@styleCode <= StyleType (2.16.840.1.1138<IP_ADDRESS>) (CWE) |
|
| CDA R1 component | Corresponding CDA R2 component | Comments |
|---|---|---|
|
levelone |
ClinicalDocument |
|
|
levelone / clinical_document_header |
NOT PRESENT |
|
|
clinical_document_header / id |
ClinicalDocument / id |
|
|
clinical_document_header / set_id |
ClinicalDocument / setId |
|
|
clinical_document_header / version_nbr |
ClinicalDocument / versionNumber |
|
|
clinical_document_header / document_type_cd |
ClinicalDocument / code |
|
|
clinical_document_header / service_tmr |
ClinicalDocument / documentationOf / serviceEvent / effectiveTime |
|
|
clinical_document_header / origination_dttm |
ClinicalDocument / effectiveTime |
|
|
clinical_document_header / copy_dttm |
ClinicalDocument / copyTime |
|
|
clinical_document_header / confidentiality_cd |
ClinicalDocument / confidentialityCode |
|
|
clinical_document_header / document_relationship |
ClinicalDocument / relatedDocument |
|
|
document_relationship / document_relationship.type_cd |
relatedDocument / @typeCode |
|
|
document_relationship / related_document |
relatedDocument / parentDocument |
|
|
document_relationship / related_document / id |
relatedDocument / parentDocument / id |
|
|
document_relationship / related_document / set_id |
relatedDocument / parentDocument / setId |
|
|
document_relationship / related_document / version_nbr |
relatedDocument / parentDocument / versionNumber |
|
|
clinical_document_header / fulfills_order |
ClinicalDocument / inFulfillmentOf |
|
|
fulfills_order / fulfills_order.type_cd |
inFulfillmentOf / @typeCode |
|
|
fulfills_order / order |
inFulfillmentOf / order |
|
|
fulfills_order / order / id |
inFulfillmentOf / order / id |
|
|
clinical_document_header / patient_encounter |
ClinicalDocument / componentOf / encompassingEncounter |
|
|
patient_encounter / id |
encompassingEncounter / id |
|
|
patient_encounter / practice_setting_cd |
encompassingEncounter / location / healthCareFacility / code |
|
|
patient_encounter / encounter_tmr |
encompassingEncounter / effectiveTime |
|
|
patient_encounter / service_location |
encompassingEncounter / location / healthCareFacility |
|
|
patient_encounter / service_location / id |
encompassingEncounter / location / healthCareFacility / id |
|
|
patient_encounter / service_location / addr |
encompassingEncounter / location / healthCareFacility / location / addr |
|
|
clinical_document_header / authenticator |
ClinicalDocument / authenticator |
|
|
authenticator / authenticator.type_cd |
authenticator / @typeCode |
|
|
authenticator / participation_tmr |
authenticator / time |
|
|
authenticator / signature_cd |
authenticator / signatureCode |
|
|
authenticator / person |
authenticator / assignedEntity / assignedPerson |
|
|
authenticator / person / id |
authenticator / assignedEntity / id |
|
|
authenticator / person / person_name |
authenticator / assignedEntity / assignedPerson / name |
|
|
authenticator / person / person_name / effective_tmr |
authenticator / assignedEntity / assignedPerson / name / validTime |
|
|
authenticator / person / person_name / nm |
authenticator / assignedEntity / assignedPerson / name |
|
|
authenticator / person / person_name / person_name.type_cd |
authenticator / assignedEntity / assignedPerson / name / @use |
|
|
authenticator / person / addr |
authenticator / assignedEntity / addr / |
|
|
authenticator / person / telecom |
authenticator / assignedEntity / telecom |
|
|
clinical_document_header / legal_authenticator |
ClinicalDocument / legalAuthenticator |
|
|
legal_authenticator / legal_authenticator.type_cd |
legalAuthenticator / @typeCode |
|
|
legal_authenticator / participation_tmr |
legalAuthenticator / time |
|
|
legal_authenticator / signature_cd |
legalAuthenticator / signatureCode |
|
|
legal_authenticator / person |
legalAuthenticator / assignedEntity / assignedPerson |
|
|
clinical_document_header / intended_recipient |
ClinicalDocument / intendedRecipient |
|
|
intended_recipient / intended_recipient.type_cd |
intendedRecipient / @typeCode |
|
|
clinical_document_header / originator |
ClinicalDocument / author |
|
|
originator / originator.type_cd |
author / @typeCode |
|
|
originator / participation_tmr |
author / time |
|
|
clinical_document_header / originating_organization |
ClinicalDocument / author ClinicalDocument / custodian |
|
|
originating_organization / originating_organization.type_cd |
custodian / @typeCode |
|
|
originating_organization / organization |
author / assignedAuthor / representedOrganization custodian / assignedCustodian / representedCustodianOrganization |
|
|
originating_organization / organization / id |
author / assignedAuthor / representedOrganization / id custodian / assignedCustodian / representedCustodianOrganization / id |
|
|
originating_organization / organization / organization.nm |
author / assignedAuthor / representedOrganization / name custodian / assignedCustodian / representedCustodianOrganization / name |
|
|
originating_organization / organization / addr |
author / assignedAuthor / representedOrganization / addr custodian / assignedCustodian / representedCustodianOrganization / addr |
|
|
clinical_document_header / transcriptionist |
ClinicalDocument / dataEnterer |
|
|
transcriptionist / transcriptionist.type_cd |
dataEnterer / @typeCode |
|
|
transcriptionist / participation_tmr |
dataEnterer / time |
|
|
clinical_document_header / provider |
ClinicalDocument / serviceEvent / performer ClinicalDocument / encompassingEncounter / responsibleParty ClinicalDocument / encompassingEncounter / encounterParticipant |
|
|
clinical_document_header / service_actor |
ClinicalDocument / participant |
|
|
service_actor / service_actor.type_cd |
participant / @typeCode |
|
|
service_actor / participation_tmr |
participant / time |
|
|
service_actor / signature_cd |
authenticator / signatureCode |
|
|
clinical_document_header / patient |
ClinicalDocument / recordTarget |
|
|
patient / patient.type_cd |
recordTarget / @typeCode |
|
|
patient / participation_tmr |
NOT PRESENT |
|
|
patient / person |
recordTarget / patientRole / patient |
|
|
patient / person / id |
recordTarget / patientRole / patient / id |
|
|
patient / is_known_by |
recordTarget / patientRole |
|
|
patient / is_known_by / id |
recordTarget / patientRole / id |
|
|
patient / is_known_by / is_known_to |
recordTarget / patientRole / providerOrganization |
|
|
patient / is_known_by / is_known_to / id |
recordTarget / patientRole / providerOrganization / id |
|
|
patient / birth_dttm |
recordTarget / patientRole / patient / birthTime |
|
|
patient / administrative_gender_cd |
recordTarget / patientRole / patient / administrativeGenderCode |
|
|
clinical_document_header / originating_device |
ClinicalDocument / author |
|
|
originating_device / originating_device.type_cd |
author / @typeCode |
|
|
originating_device / participation_tmr |
author / time |
|
|
originating_device / device |
author / assignedAuthor |
|
|
originating_device / device / id |
author / assignedAuthor / id |
|
|
originating_device / device / responsibility |
author / assignedAuthor / assignedAuthoringDevice / asMaintainedEntity |
|
|
originating_device / device / responsibility / responsibility.type_cd |
author / assignedAuthor / assignedAuthoringDevice / asMaintainedEntity / @classCode |
|
|
originating_device / device / responsibility / responsibility_tmr |
author / assignedAuthor / assignedAuthoringDevice / asMaintainedEntity / effectiveTime |
|
|
clinical_document_header / service_target |
ClinicalDocument / participant |
|
|
service_target / service_target.type_cd |
participant / @typeCode |
|
|
service_target / participation_tmr |
participant / time |
|
| CDA R1 component | Corresponding CDA R2 component | Comments |
|---|---|---|
|
levelone / body / non_xml |
ClinicalDocument / component / nonXMLBody |
|
|
levelone / body / section |
ClinicalDocument / component / structuredBody / section |
|
|
section / @originator |
section / author |
|
|
section / @confidentiality |
section / confidentialityCode |
|
|
section / @xml:lang |
section / languageCode |
|
|
section / caption |
section / title |
|
|
section / caption / link |
NOT PRESENT |
|
|
section / caption / caption_cd |
section / code |
|
|
@originator |
SEE COMMENTS |
|
|
@confidentiality |
NOT PRESENT |
|
|
@xml:lang |
@language |
|
|
content |
content |
|
|
link |
linkHtml |
|
|
coded_entry |
section / entry / act |
|
|
coded_entry / coded_entry.id |
section / entry / act / id |
|
|
coded_entry / coded_entry.value |
section / entry / act / code |
|
|
observation_media |
section / entry / observationMedia |
|
|
observation_media / observation_media.id |
section / entry / observationMedia / id |
|
|
observation_media / observation_media.value |
section / entry / observationMedia / value |
|
|
local_markup |
SEE COMMENTS |
|
|
caption |
caption |
|
|
caption / caption_cd |
@styleCode |
|
|
paragraph |
paragraph |
|
|
list |
list |
|
|
table |
table |
|
| Return to top of page |


"""
Useful functions to deal with 3D geometry
"""
# pylint: disable=invalid-name,missing-docstring,invalid-unary-operand-type,no-else-return
import numpy as np
[docs]def get_plane(a, b, c):
"""
Get plane equation from 3 points.
Returns the coefficients of `ax + by + cz + d = 0`
"""
ab = b - a
ac = c - a
x = np.cross(ab, ac)
d = -np.dot(x, a)
pl = np.hstack((x, d))
return pl
[docs]def point_plane_dist(pt, plane, signed=False):
"""
Get the signed distance from a point `pt` to a plane `plane`.
Reference: http://mathworld.wolfram.com/Point-PlaneDistance.html
Plane is of the format [A, B, C, D], where the plane equation is Ax+By+Cz+D=0
Point is of the form [x, y, z]
`signed` flag indicates whether to return signed distance.
"""
v = plane[0:3]
dist = (np.dot(v, pt) + plane[3]) / np.linalg.norm(v)
if signed:
return dist
else:
return np.abs(dist)
[docs]def edges_of(vertices):
"""
Return the vectors for the edges of the polygon defined by `vertices`.
Args:
vertices: list of vertices of the polygon.
"""
edges = []
N = len(vertices)
for i in range(N):
edge = vertices[(i + 1) % N] - vertices[i]
edges.append(edge)
return edges
[docs]def orthogonal(v):
"""
Return a 90 degree clockwise rotation of the vector `v`.
Args:
v: 2D array representing a vector.
"""
return np.array([-v[1], v[0]])
[docs]def is_separating_axis(o, p1, p2):
"""
Return True and the push vector if `o` is a separating axis of `p1` and `p2`.
Otherwise, return False and None.
Args:
o: 2D array representing a vector.
p1: 2D array of points representing a polygon.
p2: 2D array of points representing a polygon.
"""
min1, max1 = float('+inf'), float('-inf')
min2, max2 = float('+inf'), float('-inf')
for v in p1:
projection = np.dot(v, o)
min1 = min(min1, projection)
max1 = max(max1, projection)
for v in p2:
projection = np.dot(v, o)
min2 = min(min2, projection)
max2 = max(max2, projection)
if max1 >= min2 and max2 >= min1:
d = min(max2 - min1, max1 - min2)
# push a bit more than needed so the shapes do not overlap in future
# tests due to float precision
d_over_o_squared = d/np.dot(o, o) + 1e-10
pv = d_over_o_squared*o
return False, pv
else:
return True, None
[docs]def polygon_collision(p1, p2):
"""
Return True if the shapes collide. Otherwise, return False.
p1 and p2 are np.arrays, the vertices of the polygons in the
counterclockwise direction.
Source: https://hackmd.io/s/ryFmIZrsl
Args:
p1: 2D array of points representing a polygon.
p2: 2D array of points representing a polygon.
"""
edges = edges_of(p1)
edges += edges_of(p2)
orthogonals = [orthogonal(e) for e in edges]
push_vectors = []
for o in orthogonals:
separates, pv = is_separating_axis(o, p1, p2)
if separates:
# they do not collide and there is no push vector
return False
else:
push_vectors.append(pv)
return True
[docs]def polygon_area(polygon):
"""
Get the area of a polygon which is represented by a 2D array of points.
Area is computed using the Shoelace Algorithm.
Args:
polygon: 2D array of points.
"""
x = polygon[:, 0]
y = polygon[:, 1]
area = (np.dot(x, np.roll(y, -1)) -
np.dot(np.roll(x, -1), y))
return np.abs(area)/2
[docs]def polygon_intersection(poly1, poly2):
"""
Use the Sutherland-Hodgman algorithm to compute the intersection of 2 convex polygons.
"""
def line_intersection(e1, e2, s, e):
dc = e1 - e2
dp = s - e
n1 = np.cross(e1, e2)
n2 = np.cross(s, e)
n3 = 1.0 / (np.cross(dc, dp))
return np.array([(n1*dp[0] - n2*dc[0]) * n3, (n1*dp[1] - n2*dc[1]) * n3])
def is_inside_edge(p, e1, e2):
"""Return True if e is inside edge (e1, e2)"""
return np.cross(e2-e1, p-e1) >= 0
output_list = poly1
# e1 and e2 are the edge vertices for each edge in the clipping polygon
e1 = poly2[-1]
for e2 in poly2:
input_list = output_list
output_list = []
s = input_list[-1]
for e in input_list:
if is_inside_edge(e, e1, e2):
# if s in not inside edge (e1, e2)
if not is_inside_edge(s, e1, e2):
# line intersects edge hence we compute intersection point
output_list.append(line_intersection(e1, e2, s, e))
output_list.append(e)
# is s inside edge (e1, e2)
elif is_inside_edge(s, e1, e2):
output_list.append(line_intersection(e1, e2, s, e))
s = e
e1 = e2
return np.array(output_list)


GPIBInstrument
public final class GPIBInstrument : MessageBasedInstrument, InstrumentProtocol
Undocumented
-
Declaration
Swift
public var bufferSize: Int
-
Declaration
Swift
public var buffer: UnsafeMutableRawBufferPointer
-
Declaration
Swift
public var session: Session
-
Declaration
Swift
public var identifier: String
-
Declaration
Swift
public var timeout: TimeInterval
-
Declaration
Swift
public var delegate: InstrumentDelegate?
-
Declaration
Swift
public var dispatchQueue: DispatchQueue
-
Undocumented
Declaration
Swift
public init(session: Session, identifier: String)
-
Sends GPIB command bytes to the device.
- Return: Amount of written bytes
Declaration
Swift
public func sendCommand(data: ViPByte, length: UInt32) throws -> UInt32
Parameters
data
A buffer of UInt8s specifying GPIB commands
length
the length of the data buffer
-
Specifies the state of the ATN line and the local active controller state.
Throws
<#throws value description#>Declaration
Swift
public func controlAtn(mode: AtnMode) throws
Parameters
mode
Specifies the state of the ATN line and optionally the local active controller state.
-
Controls the state of the GPIB Remote Enable (REN) interface line, and optionally the remote/local state of the device.
Throws
<#throws value description#>Declaration
Swift
public func controlRen(mode: RenMode) throws
Parameters
mode
Specifies the state of the REN line and optionally the device remote/local state.
-
Tell the GPIB device at the specified address to become the controller in charge
Throws
One of the followingVISAError
errors:- .invalidSession
- .unsupportedOperation
- .resourceLocked
- .timeout
- .notControllerInCharge
- .noListeners
- .ioError
Declaration
Swift
public func passControl(primaryAddress: UInt16, secondaryAddress: UInt16) throws
Parameters
primaryAddress
Primary address of the device you want to pass control to
secondaryAddress
Secondary address of the targeted GPIB device. If the targeted device does not have a secondary address, this parameter should contain the value VI_NO_SEC_ADDR.
-
Pulses the interface clear line for at least 100 microseconds
Throws
One of the followingVISAError
errors:- .invalidSession
- .unsupportedOperation
- .resourceLocked
- .notSystemController
Declaration
Swift
public func sendIfc() throws
-
Waits for a serial request coming from the instrument doesn’t end when another instrument signals for an SRQ Keep in mind that this is a BLOCKING operation Waits for a serial request coming from the instrument Doesn’t end when another instrument signals for an SRQ Keep in mind this is a BLOCKING operation
Throws
<#throws value description#>Declaration
Swift
public func waitForSrq(timeout: UInt? = 25000) throws
Parameters
timeout
Timeout (in milliseconds) for the wait


Kogi West: PDP Issues Directives Ahead Of Supplementary Election
by Enioluwa AdeniyiThe Peoples Democratic Party on Sunday charged it members and supporters in Kogi West senatorial district to come out in their number to vote for the party in the supplementary election on November 30.
PDP in a statement through its spokesperson, Kola Ologbondiyan, stated that nothing would stop the party from picking the senate seat.
He charged all PDP members, supporters, citizens and voters in Kogi West to be united.
He urged them to be “ready against any repressive forces that might attempt to forcefully invade any polling unit, disrupt the electoral process or alter results as witnessed in the Nov. 16 elections”.
Ologbondiyan stated that Kogi state and particularly Kogi West, remains a PDP zone and the people are not ready to accept any impunity.
“Our party charges the people of Kogi to come prepared to vote, protect their votes and ensure that they stamp their will on the ballot despite the odds.”
He called on security agents a well as INEC officials against subverting the will of the people, adding that such was “capable of attracting dire consequences”.
“The party directs its members to stay united under their leaders in the area as they will continue to be updated of vital information ahead of the election.”
The PDP spokesperson stated that the party is mourning the compatriots who lost their lives during the November 16 election, he added that their death will never be in vain.


'I'm delighted José's back': Premier League managers react to Mourinho's Spurs move – video
by SNTV
Premier League managers shared their thoughts about the appointment of José Mourinho as Mauricio Pochettino's successor at Tottenham Hotspur.
Brendan Rodgers said Mourinho is a 'winner' and Graham Potter called him 'a top, top manager'.
Meanwhile Arsenal manager Unai Emery admitted he was ‘surprised’ the club decided to part ways with Pochettino and questioned Mourinho's move. He said: 'I don't know why and I don't know how he's going to change their performance'


--- layout: post title: But the devil is in the detail tags: - Software Development status: publish type: post published: true meta: _edit_last: '451289' --- BBC NEWS | Technology | Microsoft's survival strategy
a tool to teach kids what programming is like without getting too bogged down in the detailI can't help thinking that teaching children programming is simple is going to store up a load of trouble when they become middle managers and demand new features because "it's SMOP"


"ALLON "oak. (1.) The expression in the Authorized Version of Joshua 19:33, “from Allon to Zaanannim,” is more correctly rendered in the Revised Version, “from the oak in Zaanannim.” The word denotes some remarkable tree which stood near Zaanannim, and which served as a landmark. (2.) The son of Jedaiah, of the family of the Simeonites, who expelled the Hamites from the valley of Gedor (1 Chronicles 4:37).
"ALLON "oak. (1.) The expression in the Authorized Version of Joshua 19:33, “from Allon to Zaanannim,” is more correctly rendered in the Revised Version, “from the oak in Zaanannim.” The word denotes some remarkable tree which stood near Zaanannim, and which served as a landmark.
(2.) The son of Jedaiah, of the family of the Simeonites, who expelled the Hamites from the valley of Gedor (1 Chronicles 4:37).


EAST-WEST (1999) / ** 1/2 aka EST-OUEST [French; English subtitles]
Directed by Regis Wargnier. Screenplay by Sergei Bodrov, Louis Gardel, Rustam Ibragimbekov and Wargnier. Starring Sandrine Bonnaire, Oleg Menshikov, Catherine Deneuve. Running time: 120 minutes. This film is not yet rated by the MFCB. Reviewed on October 30th, 2000.
By SHANNON PATRICK SULLIVAN
It's somewhat ironic that I saw "East-West" the evening after viewing Rod Lurie's "The Contender". Both are politically charged movies which, although laudable in broad strokes, fail to achieve their full potential because they adopt an overtly simplistic approach to their subject matter. For "The Contender", it was a matter of dismissing potent dramatic issues in favour of an easy, quick-fix resolution designed to make the audience go home happy. In the case "East-West", the problem is somewhat more ingrained.
Featuring French and Russian dialogue (with English subtitles), "East-West" is the decade-spanning story of Frenchwoman Marie Golovin (Sandrine Bonnaire), whose husband Alexei (Oleg Menchikov) is one of thousands of Russians being wooed back to their homeland in the aftermath of World War II. The film, directed by Regis Wargnier, starts beautifully as we watch the homeward-bound Russians celebrating in a sumptuous ship's cabin. Then, without warning, we are deposited into the terrifying midst of the Soviet empire: as the passengers disembark, they are immediately herded into two groups, depending on whether or not the Kremlin believes them to be "imperialist spies".
Marie is initially amongst the condemned, and survives only because of the pleas of her husband, a renowned doctor. They are sent to live in a crowded residence housing several other families. Alexei becomes the head of medicine at a factory while Marie does the laundry for a military choir. They are constantly watched, though, and when the residence's supervisor makes the mistake of revealing to Marie that she knows French, she is soon relieved of her duties and taken away. The woman's grandson Sacha (Sergei Bodrov Jr), now homeless, is taken in by the Golovins. Marie, disillusioned with her husband's apparent unwillingness to stand up to the state, begins a passionate affair with Sacha. Together, they plot to escape Russia by taking advantage of Sacha's position as a member of the Soviet swim team.
"East-West" is a visual treat, as Wargnier fills the screen with contrasts that are, naturally enough, both entrancing and horrifying. The stark beauty of the Russian landscape is set tantalisingly against the sheer brutality of the Communist regime. (The snowswept image of the pond where Sacha trains, now frozen over with ice, is particularly memorable.) Scenes of romance and tenderness are tempered by the knowledge that everyone is being watched and nobody can be trusted. Even Sacha's triumph in qualifying for the national swim team is offset by the fact that it has been engineered for darker, more desperate purposes -- and the powers that be may or may not be aware of the fact.
But unfortunately, Wargnier fails to conjure a story compelling enough to live up to his stirring images. "East-West" is far too conventional in its structure, dwelling not on the oppression of the Supreme Soviet but instead on Marie's efforts to escape the country. It is the Cold War reduced to its most simplistic form -- Communism is bad, democracy is good, and shades of grey are all but nonexistent. "East-West" would have been better served if Wargnier had opted to more strongly establish the effect of the political climate on everyday Russian life. Instead, he concentrates mostly on the more extreme aspects of the regime, such as a Gestapo agent who is almost cartoonish in his villainy.
The result is that Wargnier loses touch with his characters. "East-West" is a movie that looks like a very personal drama, but is executed more like a particularly slow-moving Tom Clancy thriller. None of the leads enjoy much depth, and Menchikov is particularly ill-served by the flimsy, tepid Alexei. Both Bonnaire and Bodrov bring a lot of vitality to their roles, but have little personality. They are thinly-veiled stereotypes; Marie is the Westerner trapped behind the Iron Curtain, Sacha the Easterner rebelling against his Communist masters.
Wargnier never effectively conveys the ties between the characters. Marie and Alexei feel less like husband and wife than casual acquaintances. When their marriage begins to break down and both begin affairs with other people, it is an almost casual occurrence. "East-West" feels populated by shadows, gliding through events without every truly becoming involved in them. There is no resonance to the drama being played out.
Even Catherine Deneuve, portraying a French stage actress named Gabrielle who may be Marie's most important ally, seems to be struggling to lend substance to her character. To make matters worse, Deneuve brings such presence to the film that she dominates any scene in which she appears; Bonnaire and the others simply cannot compete. This would be fine if Gabrielle played a more central role in "East-West", but she does not; she is a facilitator, whose emotional stakes in the drama are limited at best.
Ultimately, then, "East-West" is a lovely but disaffecting drama which settles for simplicity when it should be striving for depth. Lacking the complexity of characterisation and depiction needed to effectively explore the themes it proffers, "East-West" ends up being little more than a pretty (and chilling) pictorial of the Soviet Union in the middle part of this century. This, in of itself, is not altogether without merit. "East-West", however, could have been much more.
Copyright © 2000 Shannon Patrick Sullivan. Archived at The Popcorn Gallery, http://www.physics.mun.ca/~sps/movies/East-West.html
_______________________________________________________________________ / Shannon Patrick Sullivan | "We are all in the gutter, but some of us \ |<EMAIL_ADDRESS>| are looking at the stars." - Oscar Wilde | \___________________________|__________________________________________/ | Popcorn Gallery Movie Reviews www.physics.mun.ca/~sps/movies.html | | Doctor Who: A Brief History of Time (Travel) /drwho.html |
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


The two boxes ('widgets') below are have two instances of the same 'widget' component attached to them.
The idea is that, when you click "Change color!" both change becuase the button fires a "changeColor" event on the document, and the widget components are listening for this event.
Clicking "Turn this'un off" removes the event listener for that component instance. The expected behaviour is that the one you've turned off should stop changing color, and the other should continue.
But, in Flight 1.1.1, calling this.off
removes all listeners to "changeColor" on the document.


Flyers-Maple Leafs Sums
by EndPlayFirst Period_1, Philadelphia, Myers 2 (van Riemsdyk, Farabee), 8:08. 2, Philadelphia, Lindblom 8 (Gostisbehere, Konecny), 18:28 (pp). Penalties_Shore, TOR, (tripping), 2:21; Mikheyev, TOR, (interference), 17:03.
Second Period_3, Toronto, Dermott 1 (Nylander, Matthews), 10:11. Penalties_Voracek, PHI, (hooking), 0:27; Timashov, TOR, (boarding), 10:26; Giroux, PHI, (tripping), 13:10.
Third Period_4, Toronto, Nylander 5 (Matthews, Holl), 3:58. Penalties_None.
Overtime_None. Penalties_Philadelphia bench, served by Konecny (too many men on the ice), 4:52.
Shootout_Philadelphia 2 (Konecny NG, Giroux G, Couturier G), Toronto 1 (Tavares NG, Matthews NG, NG, Nylander G).
Shots on Goal_Philadelphia 8-10-13-1_32. Toronto 10-11-11-8_40.
Power-play opportunities_Philadelphia 1 of 3; Toronto 0 of 3.
Goalies_Philadelphia, Elliott 3-2-1 (40 shots-38 saves). Toronto, Andersen 9-2-2 (32-30).
T_2:55.
Referees_Wes McCauley, Francois St Laurent. Linesmen_Devin Berg, Ryan Galloway.


--- layout: post status: publish published: true title: Binging at the plate. author: display_name: Kurt login: Kurt email<EMAIL_ADDRESS>url: '' author_login: Kurt author_email<EMAIL_ADDRESS>wordpress_id: 395 wordpress_url: http://ivyenvy.com/?p=395 date: '2009-03-25 16:24:42 +0000' date_gmt: '2009-03-25 22:24:42 +0000' categories: - Offense tags: - Brewers - Cardinals - cubs - Micah Hoffpauir - Spring Training - Jake Fox - Runs - Averages comments: - id: 155 author: Prince Fielder author_email<EMAIL_ADDRESS>author_url: '' date: '2009-03-31 15:10:26 +0000' date_gmt: '2009-03-31 21:10:26 +0000' content: The cubs are weak sauce and will not score nine runs the entire Easter weekend in Milwaukee! ---
I couldn't resist titling this post with a bad sports page headline. I also can't resist analyzing a few stats of spring training. It's been exactly one month and I've been holding off, telling myself "it's just spring training, don't get too caught up in stats". But I have to share my delight in the Cubs' scoring aptitude. The Cubs have played 29 games as of today (March 25) if you count the game vs. Japan. In those 29 games they have averaged 6.59 runs per game. For comparison sake the Brewers are averaging 5.6 and the Cards 6 runs per game. When the Cubs win they are scoring 9.13 runs per game. In their last ten games they have averaged 9.5. They laid down 20 on Oakland on Monday and 9 on Colorado yesterday. Micah Hoffpauir and Jake Fox lead the team with 13 runs a piece.
Spring training run totals are going to be skewed upward, but with less than two weeks until opening day this kind of offense is a good sign.


Robot Person
// Front End Developer & Designer
Profile
I am an experienced Design Manager, Front End Developer, Web Designer, Leader, and Art Director with a demonstrated history working in the automotive industry. I focus on promoting high attention to detail, the ability to solve creative puzzles, create innovative strategies, optimize websites for performance, and troubleshoot code. My proficiencies include HTML, CSS, SASS, JavaScript, jQuery, Bootstrap, Responsive Web Design, utilizing and creating CSS frameworks, designing corporate style guides, and Adobe Creative Suite. I am a strong arts and design professional with a Bachelor’s of Science degree focused in Digital Media.
Professional Experience
Art Director, DealerOn, Inc.
February 2018 - Present- I assisted product development teams and project managers in planning, scoping, and assessing level of effort for various projects and new products.
- Worked closely with development teams to integrate front end code with proprietary platform and CMS.
- Built wireframes, created mockups, and hand-coded HTML/CSS/JavaScript interactive mockups.
- Responsible for building official company product style guide and enforcement rules modeled after Google's Material Design language.
Manager of Creative Operations, DealerOn, Inc.
(April 2017 - February 2018)- Built the front end development team & creative operations department from scratch to work with internal platform development teams from the ground up.
- Formed groups of internal users for testing and gathering real-life application usage data to be used on internal quality of life and efficiency projects.
- Tested, designed, and built new products and features related to the company's proprietary platform and content management system.
- Built functional mockups and demonstrations to show proof of concept of multiple projects to stakeholders.
Manager of Design, DealerOn Inc.
(May 2016 - April 2017)- Managed 3 teams of web designers including front end developers.
- Conducted designer trainings for newly hired web designers and front end developers.
- Enforced compliance and style guidelines for Original Equipment Manufacturers.
Lead Web Designer, DealerOn, Inc.
(February 2015 - May 2016)- Built interactive demos for sales, marketing, and development teams.
- Assisted the team with advanced troubleshooting and problem solving.
- Created snippets of repeatable code for designers to use in the creation of websites.
Formal Education
Andrews University
Berrien Springs, MichiganGraduated May 2013: Bachelor's of Science, General Studies with an emphasis in Digital Media


Performance Benchmark
Xixibase
http://code.google.com/p/xixibase/
Source code
svn co http://xixibase.googlecode.com/svn/trunk/
Test Environment
Software
- Xixibase Server
- Version is 0.2,default install configuration.
- Start with option "-m 16000"
- Java Client
- JVM Version: Sun JDK 1.6.0_27
- JVM args: -server -Xms1024m -Xmx2048m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=64m -XX:MaxPermSize=64m
Hardware
- Server and client all run in one machine
- CPU: 4 x Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
- OS: CentOS 5.3 64bit
- RAM: 16 GiB
Case1
- StressTest (com.xixibase.cache.StressTest)
- Thread: 16
- KeyCount: 100000
- Set OPs/per thread: 100000
- Get OPs/per thread: 300000
- Total start 16 threads, every thread do 100000 'set' op and do 300000 'get' op
- Raw log: StressTest.txt
Case2
- StressTestLocalCache (com.xixibase.cache.StressTestLocalCache)
- Update Thread: 1
- Get Thread: 16
- KeyCount: 200000
- updateReplayCount: 2
- Total start 1 'update' thread and 16 'get' threads. The 'update' thread update the K/V to Xixibase server. The 'get' thread get the K/V from Xixibase server and watch the change of K/V in Xixibase server. When the watched K/V change, the client local cache will get the change immediately.
- Raw log: StressTestLocalCache.txt
- Notes: The TPS of 'get' is too bigger than other, so that we need the followed 2 charts.


Project Notes
Project:
Java to XML
Author:
G.Birbilis
Company:
Agrinio Club
Description:
Things to do...
Item 1
Item 2


Floater - Does not smoothly expand to show track
-
mikej
I've been using Synergy for years and have noticed this problem before, but have no idea how it was fixed previously.
I have just upgraded to a Mac Pro and have reinstalled from scratch rather than using the Migration Assistant, and for some reason when the Synergy floater pops up it fades in and expands to be wide enough to fit the track info in without any animation. I'm pretty sure it usually smoothly expands to show this.
Any ideas why it's doing this, or how to fix it? I've tried trashing all folders/prefs, and upgrading to the latest version, with no luck.
-
Greg Hurrell
Strange. No animation? What happens? Does it just jump there in one go? Or does it appear at already the right width? Or is there an animation, but it's not smooth?
Does the same thing happen when you try from inside another user account (just to rule out account-local causes)?
-
mikej
It appears with the album art, then instead of smoothly expanding to the right to show the track name, it just jumps to the end. I created a test user account and it behaves normally with the smooth scrolling, so it must be something to do with my profile, though I have no idea what.
-
Greg Hurrell
Well you've already tried the obvious steps (trashing the prefs, re-installing) so that rules out a couple of typical problem sources (corrupt files).
My next suspect would be something that you have installed and running under your normal account that produces the problem. Perhaps something that competes too heavily for resources.
The other possibility is that it's not Synergy's files which are corrupt in your user account but iTunes'. You could try temporarily moving your iTunes preferences out the way, probably your music library file as well (the XML file and the database, not the actual music files themselves). If there is a problem with those files it might be causing iTunes to respond sluggishly, and that could be causing Synergy to skip as well (while it waits for iTunes). There might be messages being logged to the console (by iTunes) which could shed some light on the problem.
-
mikej
I figured out what it was - I had used Onyx to set the display of sheets to faster than normal, and it seems that the floater uses that setting in some way also. I set it back to Normal and all is well again.
-
Greg Hurrell
Ah very interesting!
At a hunch, Onyx is probably doing some black magic with the NSWindow "setFrame:display:animate:" method and possibly the "animationResizeTime" method as well. It *might* be possible to work around this providing a user-settable resize time, but I don't know how Onyx works nor how deeply it injects itself into the system.
Reply
This topic is now closed.


Lazy Bendable Flexible Hang Neck Phone Holder 360 Degree Rotation Mobile Stand - Black
Rs. 345
Mini Invisible Ultra Bluetooth Mini Bluetooth Wireless Stereo Headset/Earphone/Handsfree/Headphone With Mic Universal Handsfree For Iphone For Samsung & For All Android Phones/Bluetooth Headset For All Mobiles/Special Blue Tooth Headset
Rs. 420
Tripod Stand 3110 - Portable Tripod with Carring Bag for Mobile Best for TIKTOK Videos
Rs. 527
M4 LED Sports Watch Smart Band -Black
Rs. 999
ORIGINAL STOCK 2019 i12 TWS AirPods Bluetooth 5.0 Earphone Touch Wireless Headset for iOS Android pk i9s i20 tws i30 i60 i80 - White
Rs. 1500
2020 Top Smartwatch Series 5 IWO13 T500 Bluetooth Call 44mm Smart Watch Heart Rate Monitor Blood Pressure
Rs. 4,300


--- layout: page title: "Developing Web Applications with Haskell and Yesod" prev: OEBPS/ch17.html next: OEBPS/ch18.html book_path: books/michael-snoyman-developing-web-applications-with-haskell-and-yesod-_oeb/ --- {% include JB/setup %} {% raw %}
{% endraw %}


§46-62 Eminent domain; proceedings according to chapter 101. The proceedings to be taken on behalf of the county for the condemnation of property as provided in section 46-61, shall be taken and had in accordance with chapter 101, as the same may be applicable. [L 1907, c 67, §4; RL 1925, §1953; RL 1935, §2301; RL 1945, §6102; am L 1951, c 12, §5(b); RL 1955, §141-2; HRS §46-62]
Case Notes
Section 46-61, this section, and §101-2 neither limit counties' general power of eminent domain as set out in §46-1.5(6), nor divest counties of authority to enact ordinances allowing for condemnation of land for any particular public purpose. 76 H. 46, 868 P.2d 1193.


--- title: Why Australia needs Flux permalink: about/why-flux/ layout: about tag-section: about flux tag-topic: why menu-order: 0.0 page-content: - subheading: Our politics is MIA. It’s DOA. Even worse, it’s DOS. body: 'Our politicians say one thing to get elected and then do another. Horse trading and back room deals have become more important than good policy, and the will of the people. Powerful lobby groups, and international corporations wield enormous political power, while ordinary Australians have little meaningful say in their country. ' - subheading: You wouldn’t use the same operating system for 400 years would you? body: 'Democracy is no different. Parliament is a 19th century power structure that no longer works in the modern age. The system needs to process more information every day than one could read in a lifetime. The demands for governmental specialisation and decentralisation have never been higher. Yet the gridlocks of lobbyists, party politics and hesitation block up the system. That’s why it’s time for an upgrade. ' - subheading: Flux is the redesign for our system so you can participate directly in parliament. body: 'Business as usual just won’t do. Through clever technology, Flux will divert political power and efficiency away from the gridlocked system and back to the people and the experts. ' --- {% for content in page.page-content %}
{{ content.body }}
Australian politics is broken. Traditional politicians say one thing to get elected and then do another. Horse trading and back room deals have become more important than good policy, and the will of the people. Powerful lobby groups, and international corporations wield enormous political power, while ordinary Australians have little meaningful say in their country.
Our parliament is based on the exclusivity of a nineteenth century power structure that doesn't work for the information age. When it comes to the challenges of a modern world, it's just not up to the task. As more information is produced every day than one could read in a lifetime, the demands for governmental specialisation and decentralisation have never been higher. Using some clever technology, Flux will put political power into the hands of those best suited to use it.
New policy platforms are not enough to fix this mess. “Business as usual” just won't do. Flux is here to redistribute political power, empower the Australian people through real political participation, and enable specialists to help repair bad policy. Flux will give Australia the framework it needs to meet the challenges of the 21st century head on.
We believe in democracy.
Our mission is the distribution of real political power to include all Australians.
We are a movement of political expression, not political ideology. We value the contribution of every Australian, no matter how great or small. We believe in a system which promotes autonomy, purpose, and expertise, as means to deliver excellent policy.
We seek to dismantle political apathy, by empowering the disenfranchised, and motivating a new generation of innovative Australians to take responsibility for their society.
We value people, not some people, but all people, and recognise our differences as strengths, not weaknesses.
We believe in a free and open society, characterised by freedom of speech, freedom of association, and the free flow of political ideas.
We are excited about a democracy for the information age. One which fosters constructive criticism, encourages innovation, and empowers our best and brightest.
{% endcomment %}


TDD
History
Kent Beck is credited as the TDD inventor.
Yet, he claims he just re-discovered it.
Definition
- write a "single" unit test describing an app's aspect
- run the test, which should fail because the app lacks that feature
- write "just enough" code, the simplest possible, to make the test pass
- "refactor" the code until it conforms to the simplicity criteria
- repeat, "accumulating" unit tests over time
Laws
You can't write any production code until you have first written a failing unit test.
You can't write more of a unit test than is sufficient to fail, and not compiling is failing.
You can't write more production code than is sufficient to pass the currently failing unit test.
Expected Benefits
- Less defects
- The overhead for tests will be compensated on the final phases
- TDD leads to improved design qualities in the code
Common Individual Pitfalls
- forgetting to run tests frequently
- writing too many tests at once
- writing tests that are too large or coarse-grained
- writing overly trivial tests
- writing tests for trivial code
Common Team Pitfalls
- partial adoption
- poor maintenance of the test suite
- abandoned test suite (i.e. seldom or never run)


Section 5.1 Oct 29: Properties of Determinants
Subsection 5.1.1 The Determinant
Generally, the most interesting matrices to look at are the square ones. For square matrices, there is an important number called the determinant which helps us determine if the matrix is invertible or not.
Strang lists 10 important properties of determinants in this section, and verifies them for \(2\times 2\) matrices. The verifications for general matrices aren't any harder, but they sure are longer, so I am glad he skipped them. Anyway, these properties are enough to get by when it is time to compute. In fact, clever use of these properties can save you a lot of time.
- The determinant of the identity matrix is always one: \(\det(I)=1\text{.}\)
- If we exchange two rows of a matrix, the determinant changes sign.
- The determinant is linear in each row separately. (The fancy new word here is that \(\det\) is a multilinear function.)
- If two rows are equal, then the determinant is zero.
- The row operation of “add a multiple of one row to another row” does not change the determinant of a matrix.
- If a matrix has a row of zeros, then its determinant is zero.
- If \(A\) is triangular, then \(\det(A)\) is the product of the diagonal entries of \(A\text{.}\)
- A matrix is singular if its deterimant is zero. A matrix is invertible exactly when its determinant is non-zero.
- The determinant is a multiplicative function at the level of matrices: \(\det(AB) = \det(A)\det(B)\text{.}\)
- The determinant of a matrix and its transpose are the same.
That last property can be helpful in a variety of ways: it allows us to translate all of those statements about rows into statements about columns!
Subsection 5.1.2 Sage and the Determinant
Sage has a built-in command for the determinant of a square matrix. It is just what you expect: A.determinant()
.
To be sure that this works properly, we can do it the old way, too:
Clearly, there are no row swaps used, so it is easy to see that \(\det(A) = 4\cdot (-5/2)\cdot (21/2) = -105\text{.}\)
Subsection 5.1.3 Explorations
Exploration 5.1.1. (Strang Ex 5.1.1).
If a \(4 \times 4\) matrix \(A\) has \(\det(A) = 1/2\text{,}\) find- \(\det(2A)\text{,}\)
- \(\det(-A)\text{,}\) and
- \(\det(A^2)\text{.}\)
Exploration 5.1.2. (Strang Ex 5.1.2).
If a \(3 \times 3\) matrix has \(\det(A) = -1\text{,}\) find- \(\det(\frac{1}{2}A)\text{,}\)
- \(\det(-A)\text{,}\)
- \(\det(A^2)\text{,}\) and
- \(\displaystyle \det(A^{-1})\)
Exploration 5.1.3. (Strang Ex 5.1.10).
Suppose that \(A\) is a matrix with the property that the entries in each of its rows add to zero. Solve the equation \(Ax = 0\) to prove that \(\det(A)=0\text{.}\)
Then suppose that instead the entries in each row add to one. Show that \(\det(A-I)=0\text{.}\) Does this mean that \(\det(A) = 1\text{?}\) Give an example or an argument.
Exploration 5.1.4. (Strang Ex 5.1.12).
The inverse of a \(2 \times 2\) matrix seems to have determinant \(1\) all the time:Exploration 5.1.5. (Strang Ex 5.1.14).
Use row operations to reduce these matrices to upper triangular ones, then find the determinants:Exploration 5.1.6. (Strang Ex 5.1.15).
Use row operations to simplify and compute these determinants:Exploration 5.1.7. (Strang Ex 5.1.23).
Suppose that \(A = \left( \begin{smallmatrix} 4 & 1 \\ 2 & 3 \end{smallmatrix} \right)\) and that \(\lambda\) is some number. Find \(A^2\text{,}\) \(A^{-1}\) and \(A-\lambda I\) and their determinants.
Which two numbers \(\lambda\) lead to \(\det(A-\lambda I) = 0\text{?}\)


St Aubin (photo by Val Ellis))
A sheltered drying harbour at the head of St Aubin's Bay, just west of St Helier. The small village here is a very attractive corner of the island.
Position 49° 11'14"N, 02° 10'00"W.
St Aubin's Harbour at low tide (Photo by Val Ellis)
Visiting yachts should only enter up to one hour either side of high water and moor up on the wall immediately to starboard.
Facilities include water, fuel and some repair facilities.
There is a good chandlery on the harbourside.
Last updated July 2016


Kasoa Cops Killings: Another Suspect freed
by Joyce Danso, GNAAccra, Nov. 19, GNA - The Kaneshie District Court has discharged Michael Osofo Ani, one of the suspects, allegedly involved in the murder of the two Police officers on the Kasoa-Buduburam- Aprah road on August 28, this year.
Ani was discharged after the Prosecution withdrew and substituted the charge sheet in court on Tuesday.
Currently, Eric Kojo Duah aka Sakora, is the sole accused being held on two counts of murder.
Duah whose charges were read to him in English had his plea reserved.
The court has since remanded Duah into the custody of the Bureau of National Investigations (BNI) to reappear on December 2.
Prosecuting, Assistant Superintendent of Police (ASP) Sylvester Asare informed the court, that the Police have completed its investigations into the matter hence prayed the court to withdraw the old charge sheet and substituted it with a new one.
According to ASP Asare, the docket and forwarding letter were ready and the two would be sent to the Attorney General’s Office by the close of the week.
When the new charges were read out in court, Ani name was excluded, making the court to discharge him.
Mr George Eshun who represented Duah and Ani indicated to the court that the discharge of Ani had confirmed his assertion that Ani did not in any way abetted to the crime hence he should be set free by the court.
Mr Eshun said following the development, he and his client would now prepare and put up their defence in the matter.
He further informed the court that another solicitor had been contracted in the matter and that he and the new solicitor were going to work together.
Duah is being held for allegedly gruesomely killing Sergeant Michael Dzamesi and Lance Corporal Mohammed Awal on August 28, this year at Kasoa.
The two Policemen were among a team of MTTD officers who were on task force duties on the Kasoa Buduburam- Aprah road.
The two while on duty checks stopped an unregistered Toyota Camry with Duah and Ani as the occupants but the car refused to stop.
Sergeant Dzamsei and Lance Corporal Awal managed to intercept the unregistered and Sergeant Dzamesi asked the two to come out of the car.
A struggle ensued between Dzamesi and Duah. Duah went back into the vehicle, pulled out a gun and shot Awal in the left rib and shoulder.
Dzamsei decided to run for his life and sought refuge in a grocery shop but Duah followed him to the shop and shot him three times and bolted with the car.
Police investigations later led to their arrest.
GNA


How to download virtual products which have been ordered using the Store module.
Important. Whenever you click on the 'Download' button, the file download counter is incremented regardless of the outcome.