This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Trauma Registry Project FAQ"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
| 5 || confirm validation can include constraint identifier in error message || Grant reports no, but NTDS identifiers will be provided as they are today || closed | | 5 || confirm validation can include constraint identifier in error message || Grant reports no, but NTDS identifiers will be provided as they are today || closed | ||
|- | |- | ||
− | | 6 || Do we need a code system for actEncounterCode (FLD) || Yes; | + | | 6 || Do we need a code system for actEncounterCode (FLD) || Yes; VALUE SET: ActEncounterCode (2.16.840.1.113883.1.11.13955) || Closed |
|- | |- | ||
| 7 || Should we specify section title in IG (content, not just presence) || Yes; "should" for title. Text is up to implementer. || Closed | | 7 || Should we specify section title in IG (content, not just presence) || Yes; "should" for title. Text is up to implementer. || Closed |
Revision as of 14:56, 8 September 2014
Back to Trauma Registry page
Modeling
# | Question | Answer | Status |
---|---|---|---|
1 | How do we distinguish a patient who has no prehospital section because there was no EMS engagement from a patient who who has no prehospital section because the data is missing? | The prehospital section can contain a null flavor of "not applicable" ("NA") meaning that there was no such event (i.e., the patient was a walk-in) or of "unknown" ("UNK") meaning that the information is not available. | Resolved |
2 | How are identifiers assigned? |
|
Resolved |
3 | Are time zones required on time stamps? | Yes | Resolved |
4 | Are time intervals inclusive or exclusive? | The abstract data types specification stipulates no default assumption, but the IVL pattern does support the Boolean properties lowClosed and highClosed that allow the user to specify the boundary type. | Resolved |
5 | confirm validation can include constraint identifier in error message | Grant reports no, but NTDS identifiers will be provided as they are today | closed |
6 | Do we need a code system for actEncounterCode (FLD) | Yes; VALUE SET: ActEncounterCode (2.16.840.1.113883.1.11.13955) | Closed |
7 | Should we specify section title in IG (content, not just presence) | Yes; "should" for title. Text is up to implementer. | Closed |
8 | Put last modified date in version rather than create? | See #2. | Closed |
9 | May need to break Transport Mode into two templates | One template, two paths; make sure DI can read this. | Resolved |
10 | Value sets without enumerated members are not listed in appendix: Trifolia issue | Listing can be forced. | Closed. |
11 | Missing LOINCs | Most received; some questions on missing items, and address codes requested. AAAM question seems close to resolution; still awaiting closure from LOINC. | Open |
12 | Need question codes for coded address elements | "ANSI FIPS" now in GNIS: use GNIS pending ACS approval | Open |
Terminology
# | Question | Answer | Status |
---|---|---|---|
1 | (age units) Minutes in HL7 not in NTDS; Weeks in HL7 not in NTDS | I don't recall deciding to add these, so we should probably remove those two.
NEMSIS has minutes but not weeks. |
Open |
2 | Industry incorrect | I don't know why LOINC assigned some codes and not others. We should use the NAICS top-level values, not the LOINC answer codes. | Open |
3 | Any long list incomplete (e.g. industry) | can we set up Trifolia for this, or do we need to publish a spreadsheet (or use PHIN VADS or VSAC). No: we need to publish some other way. | Open |
4 | Code for “Other Race” is in NTDS but not in HL7 | We propose to use "OTH" flavor of null | Open |
5 | LA17105-0 - Patient Chemically paralyzed – In HL7 is not a NTDS code | Included based on harmonization with NEMSIS | Closed |
6 | LA17388-2 No airbag present – Not an NTDS code and currently the represented NA – null flavor case. This is the only case where I found a NTDS Null coded into a LOINC code. | Included based on harmonization with NEMSIS. And "not present" isn't really a null. | Closed |
7 | Protective Devices: Code Distinction issue – The lap and shoulder belt codes now contain the ‘Only’ description which is not accurate to the existing NTDS codes. | Included based on harmonization with NEMSIS | Closed |
8 | Child seat breakdown now in protective devices, no distinct field/element? | Included based on harmonization with NEMSIS | Closed |
9 | No code for “Airbag Present” | Based on harmonization with NEMSIS--Airbag status contains this information | Closed |
10 | No code for ‘Other’ protective devices | We propose to use "OTH" flavor of null | Closed |
11 | Need country codes | Use VS 2.16.840.1.113883.3.88.12.80.63 (HITSP), system 1.0.3166.2.2.2, name Country Codes | Closed |
12 | Need State codes | Use VS 2.16.840.1.113883.3.88.12.80.1 (HITSP), system "NA", name FIPS 5-2 (State) (available at http://www.census.gov/geo/reference/ansi_statetables.html) | Closed |
13 | Need County codes | Use VS "NA", system "NA", name FIPS 6-4 (County) (available at http://www.census.gov/geo/reference/codes/cou.html) | Closed |
14 | Need City codes | Use VS "NA", system "NA", name ANSI Codes for Places (available at http://www.census.gov/geo/reference/codes/place.html). Or, NEMSIS uses GNIS, available at http://geonames.usgs.gov/domestic/download_data.htm | Open |