Detailed Cross Analysis for the participantliving.
| ParticipantLiving.birthDate |
| ParticipantLiving.birthDate : date [0..1] |
| Resource | Matches | Issues | Tasks | Status | Notes |
| Patient | - Patient.birthDate : date [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
birthDate does not contain the recommended logical text for short (Pattern: The date of birth for the patient; ; Resource: The date of birth for the individual) - no reason provided
birthDate does not contain the recommended logical text for definition (Pattern: The date when the patient was born.; ; Resource: The date of birth for the individual.) - no reason provided
birthDate does not contain the recommended logical text for requirements (Pattern: Used for identity verification and may drive other business processes.; ; Resource: Age of the individual drives many clinical processes.) - no reason provided
| | | |
| Practitioner | - Practitioner.birthDate : date [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
birthDate does not contain the recommended logical text for short (Pattern: The date of birth for the practitioner; ; Resource: The date on which the practitioner was born) - no reason provided
birthDate does not contain the recommended logical text for definition (Pattern: The date when the practitioner was born.; ; Resource: The date of birth for the practitioner.) - no reason provided
birthDate does not contain the recommended logical text for requirements (Pattern: Used for identity verification and may drive other business processes.; ; Resource: Needed for identification.) - no reason provided
| | | |
| RelatedPerson | - RelatedPerson.birthDate : date [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
birthDate does not contain the recommended logical text for short (Pattern: The date of birth for the related person; ; Resource: The date on which the related person was born) - no reason provided
birthDate does not contain the recommended logical text for definition (Pattern: The date when the related person was born.; ; Resource: The date on which the related person was born.) - no reason provided
birthDate does not contain the recommended logical text for requirements (Pattern: Used for identity verification and may drive other business processes.; ; Resource: ) - no reason provided
| | | |
| ParticipantLiving.gender |
| ParticipantLiving.gender : code [0..1] |
| Resource | Matches | Issues | Tasks | Status | Notes |
| Patient | - Patient.gender : code [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
| | | |
| Practitioner | - Practitioner.gender : code [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
gender does not contain the recommended logical text for definition (Pattern: Administrative Gender - the gender that the practitioner is considered to have for administration and record keeping purposes.; ; Resource: Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.) - no reason provided
gender does not contain the recommended logical text for requirements (Pattern: Needed for identification of the individual, in combination with (at least) name and birth date.; ; Resource: Needed to address the person correctly.) - no reason provided
| | | |
| RelatedPerson | - RelatedPerson.gender : code [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
gender does not contain the recommended logical text for definition (Pattern: Administrative Gender - the gender that the related person is considered to have for administration and record keeping purposes.; ; Resource: Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.) - no reason provided
gender does not contain the recommended logical text for requirements (Pattern: Needed for identification of the individual, in combination with (at least) name and birth date.; ; Resource: Needed for identification of the person, in combination with (at least) name and birth date.) - no reason provided
| | | |
| ParticipantLiving.photo |
| ParticipantLiving.photo : Attachment [0..*] |
| Resource | Matches | Issues | Tasks | Status | Notes |
| Patient | - Patient.photo : Attachment [0..*]
photo does not contain the recommended logical text for short (Pattern: Image of the {{title}; ; Resource: Image of the patient) - no reason provided
photo does not contain the recommended logical text for definition (Pattern: A facial image of the patient.; ; Resource: Image of the patient.) - no reason provided
photo does not contain the recommended logical text for requirements (Pattern: Many EHR systems have the capability to capture an image of the participant. Fits with newer social media usage too.; ; Resource: Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too.) - no reason provided
| | | |
| Practitioner | - Practitioner.photo : Attachment [0..*]
photo does not contain the recommended logical text for short (Pattern: Image of the {{title}; ; Resource: Image of the person) - no reason provided
photo does not contain the recommended logical text for definition (Pattern: A facial image of the practitioner.; ; Resource: Image of the person.) - no reason provided
photo does not contain the recommended logical text for requirements (Pattern: Many EHR systems have the capability to capture an image of the participant. Fits with newer social media usage too.; ; Resource: Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too.) - no reason provided
| | | |
| RelatedPerson | - RelatedPerson.photo : Attachment [0..*]
photo does not contain the recommended logical text for short (Pattern: Image of the {{title}; ; Resource: Image of the person) - no reason provided
photo does not contain the recommended logical text for definition (Pattern: A facial image of the related person.; ; Resource: Image of the person.) - no reason provided
photo does not contain the recommended logical text for requirements (Pattern: Many EHR systems have the capability to capture an image of the participant. Fits with newer social media usage too.; ; Resource: Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.) - no reason provided
| | | |
| ParticipantLiving.communication |
| ParticipantLiving.communication : CodeableConcept [0..*] |
| Resource | Matches | Issues | Tasks | Status | Notes |
| Patient | - Patient.communication : BackboneElement [0..*]
Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided
Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided
Only one element has bindings (Pattern: true; ; Resource: false) - no reason provided
communication does not contain the recommended logical text for short (Pattern: Language used by patient; ; Resource: A language which may be used to communicate with the patient about his or her health) - no reason provided
communication does not contain the recommended logical text for definition (Pattern: The language which can be used to communicate with the patient.; ; Resource: A language which may be used to communicate with the patient about his or her health.) - no reason provided
communication does not contain the recommended logical text for comments (Pattern: The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.; ; Resource: If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.) - no reason provided
communication does not contain the recommended logical text for requirements (Pattern: Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.; ; Resource: If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.) - no reason provided
| Type Mismatch. | | |
| RelatedPerson | - RelatedPerson.communication : BackboneElement [0..*]
Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided
Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided
Only one element has bindings (Pattern: true; ; Resource: false) - no reason provided
communication does not contain the recommended logical text for short (Pattern: Language used by related person; ; Resource: A language which may be used to communicate with the related person about the patient's health) - no reason provided
communication does not contain the recommended logical text for definition (Pattern: The language which can be used to communicate with the related person.; ; Resource: A language which may be used to communicate with the related person about the patient's health.) - no reason provided
communication does not contain the recommended logical text for comments (Pattern: The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.; ; Resource: If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.) - no reason provided
communication does not contain the recommended logical text for requirements (Pattern: Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.; ; Resource: If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.) - no reason provided
| Type Mismatch. | | |
Workflow
|
Propose a change