Xác định mục đích sử dụng của mã định danh (usual, official, temp, secondary)

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Loại mã định danh được sử dụng. Bắt buộc phải có MR (Medical Record Number) và NI (National Identifier)

Allows users to make use of identifiers when the identifier system is not known.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

URI định danh hệ thống cấp mã cho identifier

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Identifier.system is always case sensitive.

Giá trị cụ thể của mã định danh bệnh nhân

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Trạng thái hoạt động của hồ sơ bệnh nhân (true: đang hoạt động, false: không hoạt động)

Need to be able to mark a patient record as not to be used because it was created in error.

If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.

This resource is generally assumed to be active if no value is provided for the active element

Xác định mục đích sử dụng của tên (usual, official, nickname, old, maiden)

Allows the appropriate name for a particular context of use to be selected from among a set of names.

Applications can assume that a name is current unless it explicitly says that it is temporary or old.

The use of a human name.

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

A renderable, unencoded form.

Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

Họ của bệnh nhân theo quy định đặt tên của Việt Nam

Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).

Tên và tên đệm của bệnh nhân theo quy định đặt tên của Việt Nam

If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.

Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.

Indicates the period of time when this name was valid for the named person.

Allows names to be placed in historical context.

Loại phương thức liên hệ (phone, email, fax, pager, url, sms, other)

Telecommunications form for contact point.

Giá trị cụ thể của phương thức liên hệ (số điện thoại, địa chỉ email)

Need to support legacy numbers that are not in a tightly controlled format.

Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.

Mục đích sử dụng của thông tin liên hệ (home, work, temp, old, mobile)

Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

Applications can assume that a contact is current unless it explicitly says that it is temporary or old.

Use of contact point.

Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.

Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Time period when the contact point was/is in use.

Giới tính của bệnh nhân theo quy định của Việt Nam (male, female, other, unknown)

Needed for identification of the individual, in combination with (at least) name and birth date.

The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.

The gender of a person used for administrative purposes.

Ngày sinh của bệnh nhân theo định dạng YYYY-MM-DD

Age of the individual drives many clinical processes.

At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).

Mục đích sử dụng của địa chỉ (home, work, temp, old, billing)

Allows an appropriate address to be chosen from a list of many.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Loại địa chỉ (postal, physical, both)

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

A renderable, unencoded form.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

Địa chỉ chi tiết (số nhà, tên đường, khu phố, thôn, xóm)

Tên thành phố (nếu bệnh nhân ở thành phố, để trống nếu ở tỉnh)

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

Mã tỉnh/thành phố theo cấu trúc hành chính Việt Nam

Mã bưu chính theo hệ thống mã bưu chính Việt Nam

Tên quốc gia theo chuẩn ISO 3166-1 alpha-2 (VN cho Việt Nam)

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

Tình trạng hôn nhân của bệnh nhân theo quy định của Việt Nam

Most, if not all systems capture it.

The domestic partnership status of a person.

Ảnh chụp của bệnh nhân

Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too.

Guidelines:

• Use id photos, not clinical photos.
• Limit dimensions to thumbnail.
• Keep byte count low to ease resource updates.

Mối quan hệ của người liên hệ với bệnh nhân

Used to determine which contact person is the most relevant to approach, depending on circumstances.

The nature of the relationship between a patient and a contact person for that patient.

Họ và tên của người liên hệ

Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person.

Thông tin liên hệ của người liên hệ (điện thoại, email)

People have (primary) ways to contact them in some way such as phone, email.

Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.

Địa chỉ nơi ở của người liên hệ

Need to keep track where the contact person can be contacted per postal mail or visited.

Giới tính của người liên hệ

Needed to address the person correctly.

The gender of a person used for administrative purposes.

Tổ chức mà người liên hệ đại diện (nếu có)

For guardians or business related contacts, the organization is relevant.

The period during which this contact person or organization is valid to be contacted relating to this patient.

Ngôn ngữ chính mà bệnh nhân sử dụng để giao tiếp

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.

The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

A human language.

Chỉ ra đây có phải là ngôn ngữ ưa thích của bệnh nhân hay không

People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.

This language is specifically identified for communicating healthcare information.

Tham chiếu đến bác sĩ gia đình hoặc bác sĩ chăm sóc chính của bệnh nhân

This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.

Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.

Tham chiếu đến tổ chức y tế chịu trách nhiệm quản lý hồ sơ bệnh nhân

Need to know who recognizes this patient record, manages and updates it.

There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).

Tham chiếu đến bệnh nhân hoặc RelatedPerson liên kết

Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual.

Loại mối quan hệ liên kết giữa các bản ghi bệnh nhân

The type of link between this patient resource and another patient resource.